Skip to content
AirgateDocumentation

VMware Workspace ONE UEM

Connect Airgate to Workspace ONE UEM (AirWatch) as a context server and call its REST API from access rules; device compliance sync is planned.

The VMware Workspace ONE (AirWatch) context server type stores the connection (base URL, credentials, trusted CA) to Workspace ONE UEM (formerly AirWatch), so Airgate HTTP actions can call the Workspace ONE UEM 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 Workspace ONE UEM 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.

  • The type defaults to Basic / user + password and supports every authentication type: None, Bearer token, API key and OAuth2 client credentials (with Token URL). With API key authentication, the type also offers API key header and API key prefix.
  • 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.
  • A Workspace ONE UEM admin account with API access, and the REST API key of your organization group (Groups & Settings › All Settings › System › Advanced › API › REST API).
  • The Workspace ONE UEM 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 VMware Workspace ONE (AirWatch) and fill in:

    Field Value
    Name WorkspaceONE
    Base URL https://as1234.awmdm.com
    Authentication Basic / user + password (or the type the API needs)
    Test path /API/system/info
  3. Workspace ONE expects the REST API key in an aw-tenant-code header. Under Server headers, add aw-tenant-code with the key and mark it sensitive, and add Accept = application/json.

  4. Save, then select Test connection.

  1. Select Context actions and Add action, and pick the Context server WorkspaceONE.
  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.

For example, look up the device by its MAC address and store its compliance state on the Airgate device record:

Field Value
Method GET
URL /API/mdm/devices?searchby=Macaddress&id=%{Connection:Client-Mac-Address-NoDelim}
Response attributes ComplianceStatus → Workspace ONE Compliance

Check the path and field names against the Workspace ONE API reference of your version.

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.