Skip to content
AirgateDocumentation

Infoblox

Connect Airgate to Infoblox NIOS as an Infoblox context server and call the WAPI REST API from access rules with HTTP actions.

The Infoblox context server type stores the connection to an Infoblox Grid Manager so HTTP actions can call the WAPI REST API from an access rule, for example to record a device’s user or role on its IPAM or DHCP object.

Status: Available as an HTTP action target. There is no built-in preset: you write the WAPI call yourself. Importing IP and host data from Infoblox into Airgate’s device records is Planned.

  • The server type defaults to Basic / user + password (WAPI’s usual authentication) and supports every other type.
  • Test connection sends GET to Test path; any answer other than 401, 403 or 5xx is a success (“reachable (HTTP N)”).
  • Actions are ordinary HTTP actions: JSON bodies with %{…} references, JSON-encoded. Response attributes can store values from the WAPI answer on the device (for example _ref).
  • An Infoblox admin user with API access and the permissions the call needs.
  • The Grid Manager reachable from Airgate over HTTPS.
  • An Airgate administrator with admin:write.
  1. Open Settings › Webhooks, select Context servers and Add context server.

  2. Choose Infoblox and fill in:

    Field Value
    Name Infoblox
    Base URL https://gm.contoso.com
    Authentication Basic / user + password
    Test path /wapi/v2.12/grid (use your WAPI version)
  3. Save, then select Test connection.

  1. Select Context actions and Add action (no preset), and pick the Context server Infoblox.

  2. Fill in the WAPI call. For example, a GET that looks up the DHCP lease of the device’s MAC and stores the leased address:

    Field Value
    Method GET
    URL /wapi/v2.12/lease?hardware=%{mac}&_return_as_object=1
    Response attributes result[0].address → Infoblox Lease IP

    In the URL, values after ? are query-encoded.

  3. Save, then Test › Render only and 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 WAPI answer; with response attributes, the device’s Attributes show the stored value.

Symptom Cause Fix
Test: authentication rejected (HTTP 401) Wrong user or password, or the user has no API access. Check the admin group’s API permission.
HTTP 400 from WAPI Unsupported WAPI version or field. Use the WAPI version of your Grid (/wapi/v2.x/).
No response attribute written The JSON path does not match the answer. Check the answer in the Execution log and adjust the path.