Skip to content
AirgateDocumentation

Juniper Networks SRX

Connect Airgate to a Juniper SRX firewall as a Juniper Networks SRX context server and call its web APIs from access rules with HTTP actions.

The Juniper Networks SRX context server type stores the connection to an SRX firewall (base URL, credentials, trusted CA) so HTTP actions can call it from an access rule, for example to send user identities to the SRX’s identity web API.

Status: Available as an HTTP action target. There is no built-in preset for SRX: you write the action’s URL and body from the Junos documentation. Built-in user identity sharing with session start and stop, like Palo Alto User-ID, is Planned.

To use an SRX or an EX switch as a RADIUS client of Airgate, see Juniper EX and Mist.

  • The server type defaults to Basic / user + password and supports every authentication type (None, Bearer token, API key, OAuth2 client credentials).
  • Test connection sends GET to Test path (a path or absolute URL; empty = the base URL). Any answer other than 401, 403 or 5xx is a success (“reachable (HTTP N)”).
  • Actions use the same templates as every HTTP action: %{user}, %{ip}, %{domain}, %{role}, %{Tips:Role}… In an application/xml body, values are XML-escaped.
  • The SRX web API you want to call enabled on the firewall, and an account or token for it.
  • The SRX reachable from Airgate over HTTPS.
  • An Airgate administrator with admin:write.
  1. Open Settings › Webhooks, select Context servers and Add context server.
  2. Choose Juniper Networks SRX and fill in Name (srx1), Base URL (for example https://srx1.contoso.com:8443), Authentication and the credentials. Set Test path to an endpoint of the API that answers GET.
  3. Turn on Verify the server certificate and paste the SRX’s CA into Trusted CA certificate(s) when it is private.
  4. Save, then select Test connection.
  1. Select Context actions and Add action (no preset).
  2. Pick the Context server srx1 and fill in Method, URL, Content type and Body as the SRX API expects. Use %{user}, %{ip}, %{domain} and %{Tips:Role} for the identity values.
  3. Save, then Test with Render only to check the request before Send request.

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 the HTTP status and the SRX’s answer.