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.
How it works
Section titled “How it works”- The server type defaults to Basic / user + password (WAPI’s usual authentication) and supports every other type.
- Test connection sends
GETto Test path; any answer other than401,403or5xxis 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).
Before you begin
Section titled “Before you begin”- 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.
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 Infoblox and fill in:
Field Value Name InfobloxBase URL https://gm.contoso.comAuthentication Basic / user + password Test path /wapi/v2.12/grid(use your WAPI version) -
Save, then select Test connection.
Step 2: Add an action
Section titled “Step 2: Add an action”-
Select Context actions and Add action (no preset), and pick the Context server
Infoblox. -
Fill in the WAPI call. For example, a
GETthat looks up the DHCP lease of the device’s MAC and stores the leased address:Field Value Method GETURL /wapi/v2.12/lease?hardware=%{mac}&_return_as_object=1Response attributes result[0].address→Infoblox Lease IPIn the URL, values after
?are query-encoded. -
Save, then Test › Render only and Send request.
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 the HTTP status and the WAPI answer; with response attributes, the device’s Attributes show the stored value.
Troubleshooting
Section titled “Troubleshooting”| 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. |