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: OIDC → Create
AI-generatedSummary
Creates a new OpenID Connect (OIDC) authentication profile in Infoblox Portal by POSTing a request body to /api/authn/v1/profiles/oidc.
Inputs
- Fields (dataFields) (required) — Resource mapper of body fields for the OIDC profile. Columns are loaded from the Infoblox Authnapi Swagger spec (read-only fields, id and _ref are skipped). Can be mapped manually or auto-mapped from input data.
- JSON Body (jsonBody) — Extra request body as JSON, merged over the mapped fields. Its keys override mapped fields with the same name. Use for fields not in the schema.
- Query Parameters — Optional name/value pairs appended to the request query string.
Output shape
One output item per input item: the JSON response from the Infoblox API, normally the newly created OIDC profile record.
Non-object responses are wrapped as {result: value}. With Continue On Fail enabled, errors are returned as {error: message} for that item. Requires Infoblox CSP API credentials.
Examples
Example 1: Register an OIDC identity provider for SSO
Resource: Auth Profile: OIDC, Operation: Create. Map required fields such as name and the provider's client and issuer settings in Fields, or supply them in JSON Body.
Example 2: Create a profile with a field missing from the schema
Leave Fields mostly empty and put the full profile definition in JSON Body, e.g. {"name":"corp-oidc", ...}.