SAP Afaria
Connect Airgate to an SAP Afaria server as a context server and call its HTTP API from access rules; device compliance sync is planned.
The SAP Afaria context server type stores the connection (base URL, credentials, trusted CA) to SAP Afaria, so Airgate HTTP actions can call the Afaria API from an access rule, for example to look up the device or record its network sign-in.
Status: Available as an HTTP action target; device compliance sync is Planned. There is no built-in preset for this type.
Unlike Microsoft Intune and
Jamf Pro, Airgate does not poll Afaria for
its devices yet: Synchronise devices (MDM poller) is not offered for
this type, and the API rejects it with config.mdm_sync is only supported for intune, jamf, crowdstrike and sentinelone servers. Access rules
therefore cannot test its management or compliance state (Managed by an
MDM and MDM compliance are written only by Intune and Jamf Pro). See
Planned integrations.
How it works
Section titled “How it works”- 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
GETto Test path (a path or an absolute URL; empty = the base URL). Any answer other than401,403or5xxis 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.
Before you begin
Section titled “Before you begin”- An Afaria account that can use its HTTP API.
- The Afaria API reachable from Airgate over HTTPS.
- An Airgate administrator with
admin:write.
Step 1: Add the context server
Section titled “Step 1: Add the context server”-
Open Settings › Webhooks, select Context servers and Add context server.
-
Choose SAP Afaria and fill in:
Field Value Name AfariaBase URL https://afaria.contoso.comAuthentication Basic / user + password (or the type the API needs) Test path an API endpoint that answers GET(empty = the base URL) -
Save, then select Test connection.
Step 2: Add an action
Section titled “Step 2: Add an action”- Select Context actions and Add action, and pick the Context
server
Afaria. - Fill in Method, URL (relative to the base URL), Content type and Body.
- Save, then select Test, enter a Client MAC or Username and use Render only before Send request.
Write the URL and body from the Afaria API documentation, using
%{mac}, %{user} or %{machine} for the device and user.
Step 3: Run the action from policy
Section titled “Step 3: Run the action from policy”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.
Verify
Section titled “Verify”Settings › Webhooks › Execution log shows each run with Source, the HTTP status and the request and response.
Troubleshooting
Section titled “Troubleshooting”| 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. |