Skip to content
AirgateDocumentation

Aruba IntroSpect

Connect Airgate to Aruba IntroSpect as a context server and send it identity and device context from access rules with HTTP actions.

The Aruba IntroSpect context server type stores the connection (base URL, credentials, trusted CA) to Aruba IntroSpect, so Airgate HTTP actions can send it the user, IP address and role of a network sign-in from an access rule.

Status: Available as an HTTP action target. Receiving risk scores or alerts from IntroSpect is Planned. There is no built-in preset for this type.

  • The type defaults to Basic / user + password and supports every authentication type: None, Bearer token, API key and OAuth2 client credentials (with Token URL).
  • Test connection sends GET to Test path (a path or an absolute URL; empty = the base URL). Any answer other than 401, 403 or 5xx is a success (“reachable (HTTP N)”).
  • Actions run after the authentication decision of the rule they are attached to. Their Response attributes can write values from a 2xx JSON answer to the device record, where later sign-ins can test them.
  • An IntroSpect account or token for its HTTP API.
  • The IntroSpect API reachable from Airgate over HTTPS.
  • An Airgate administrator with admin:write.
  1. Open Settings › Webhooks, select Context servers and Add context server.

  2. Choose Aruba IntroSpect and fill in:

    Field Value
    Name IntroSpect
    Base URL https://introspect.contoso.com
    Authentication Basic / user + password (or the type the API needs)
    Test path an API endpoint that answers GET (empty = the base URL)
  3. Save, then select Test connection.

  1. Select Context actions and Add action, and pick the Context server IntroSpect.
  2. Fill in Method, URL (relative to the base URL), Content type and Body.
  3. Save, then select Test, enter a Client MAC or Username and use Render only before Send request.

Write the URL and body from the IntroSpect API documentation. Useful values: %{user}, %{ip}, %{mac}, %{Tips:Role}, %{Endpoint:Category}.

Create an HTTP enforcement profile ({"context_action_id": "<id>"}) and attach it to a rule through the API; see Webhooks and HTTP actions, Step 3.

Settings › Webhooks › Execution log shows each run with Source, the HTTP status and the request and response.

Symptom Cause Fix
Test: authentication rejected (HTTP 401) or (HTTP 403) Wrong credentials, or a required API header is missing. Check Authentication and Server headers.
Test: server error (HTTP 5xx) Test path points at an endpoint that fails on a plain GET. Use a simple read endpoint.
No response attribute written The answer was not 2xx JSON, the JSON path does not match, or the request had no device MAC. Open the run in the Execution log.