Skip to content
AirgateDocumentation

IBM MaaS360

Connect Airgate to IBM MaaS360 as a context server and call its web services from access rules; device compliance sync is planned.

The IBM MaaS360 context server type stores the connection (base URL, credentials, trusted CA) to IBM MaaS360, so Airgate HTTP actions can call the MaaS360 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 MaaS360 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).
  • 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 MaaS360 administrator with web services access.
  • An authentication method the MaaS360 API accepts and Airgate supports (see below). Airgate does not run a separate vendor-specific login call before an action.
  • The MaaS360 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 IBM MaaS360 and fill in:

    Field Value
    Name MaaS360
    Base URL the API host of your MaaS360 instance, for example https://services.fiberlink.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 MaaS360.
  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 MaaS360 web services reference, using %{mac}, %{user} or %{Connection:Client-Mac-Address-NoDelim} for the device and user.

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.