Actions182
- Address Block Actions
- Audit Log Actions
- Auth Profile: LDAP Actions
- Auth Profile: OIDC Actions
- Auth Profile: SAML Actions
- CDC Application Actions
- CDC Destination: HTTP Actions
- CDC Destination: Splunk Actions
- CDC Destination: Syslog Actions
- CDC Host Actions
- Custom API Request Actions
- DFP Service Actions
- DHCP Fingerprint Actions
- DHCP Lease Actions
- DNS Event Actions
- DNS Record Actions
- DNS Zone Actions
- Endpoint Device Group Actions
- Endpoint Roaming Device Actions
- Endpoint VPN Profile Actions
- Fixed Address Actions
- Global Search Actions
- Identity: Compartment Actions
- Identity: Group Actions
- Identity: User Actions
- Infrastructure Host Actions
- Infrastructure Service Actions
- IP Address Actions
- IP Space Actions
- IPAM Range Actions
- Location Actions
- Lookalike Domain Actions
- Lookalike Target Actions
- NIOS Custom API Request Actions
- NIOS WAPI Object Actions
- NTP Service Config Actions
- Redirect: Custom Redirect Actions
- Service Log Actions
- SOC Insight Actions
- Subnet Actions
- TD Access Code Actions
- TD Application Filter Actions
- TD Category Filter Actions
- TD Internal Domain List Actions
- TD Named List Actions
- TD Scheduled Report Actions
- TIDE Batch Actions
- TIDE Dossier Lookup Actions
- TIDE Threat Actions
Auth Profile: LDAP → Create
AI-generatedSummary
Creates a new LDAP authentication profile in Infoblox Portal by sending a POST to /api/authn/v1/profiles/ldap with a body built from mapped fields and optional JSON.
Inputs
- Fields (dataFields) (required) — Resource mapper listing writable fields from the Infoblox Authnapi swagger schema (fetched live from the realm). Required schema fields are listed first. Values are used as the request body. If the schema can't load, use JSON Body instead.
- JSON Body (jsonBody) — JSON object merged over the mapped fields, so its keys override mapped ones. Use for fields not in the schema. Defaults to {}.
- Query Parameters — Optional name/value pairs appended to the request URL as query string parameters.
Output shape
One item per input item containing the API response for the created LDAP profile, as returned by Infoblox.
Non-object responses are wrapped as {result: value}. With Continue On Fail enabled, failures yield an item with an
errormessage. Requires Infoblox CSP API credentials. Invalid JSON in JSON Body throws a parse error.
Examples
Example 1: Create an LDAP profile with fields chosen from the schema
Resource: Auth Profile: LDAP, Operation: Create; add required fields (e.g. name, server settings) in Fields mapper.
Example 2: Create a profile using a raw payload
Put the full profile definition as an object in JSON Body, e.g. {"name":"corp-ldap",...}, leaving Fields empty.