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 → Update
AI-generatedSummary
Updates an Infoblox OIDC authentication profile identified by its resource ID. Sends the mapped fields merged with the optional JSON body to the profile endpoint using an HTTP PUT request.
Inputs
- Resource ID (required) — Infoblox resource ID of the OIDC authentication profile to update.
- Fields (required) — Map the profile fields to update. Automatically mapped values are combined with the JSON Body; JSON Body keys take precedence when they overlap.
- JSON Body — Optional JSON fields merged over the mapped fields. Use for fields unavailable in the mapper or when no schema is available.
- Query Parameters — Optional additional query parameters sent with the request.
Output shape
A single record or a list of records, depending on the API response.
The node wraps a non-array response as one output item; array responses are emitted as multiple items. With Continue On Fail enabled, an item-level error message is returned instead.