AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node updates an existing Enterprise Connection by sending specified update data to the corresponding API endpoint. It is useful for managing enterprise identity provider (IDP) connections, allowing users to modify connection details such as display name, default roles, organization IDs, and IDP type.

Common scenarios include:

  • Changing the display name of an enterprise connection for better identification.
  • Updating role defaults or role mappings to control user permissions.
  • Switching or configuring the identity provider type (e.g., OpenID, Okta, Azure, Google).
  • Adjusting organizational associations for the connection.

Practical example: A company wants to rename an existing enterprise connection from "Old Connection" to "New Connection" and change its default role to "Read Only". This node can perform that update in a single operation.

Properties

Name Meaning
Id The unique numeric identifier of the enterprise connection to update.
Options JSON object containing strategy-dependent options for the enterprise connection. The exact attributes depend on the connection's strategy and should be checked individually.
Additional Body Fields Optional additional fields to include in the update request body:
- Organization Id: Numeric ID of the organization.
- Default Organization Id: Numeric ID of the default organization.
- Display Name: UI-visible name of the connection.
- Role Default: Default role assigned; options are Administrator, Read Only, Owner, Technical, Accountant, Policies Only, Super Administrator.
- Role Map: JSON array defining role mappings.
- Idp: Type of the enterprise connection's identity provider; options are Openid, Okta, Azure, Google.

Output

The node outputs JSON data representing the updated enterprise connection as returned by the API. This typically includes all current properties of the connection after the update, such as IDs, names, roles, and configuration details.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the external service managing enterprise connections.
  • The node sends HTTP requests with JSON bodies to the configured API endpoint.
  • Proper network access and valid credentials must be configured in n8n for successful operation.

Troubleshooting

  • Invalid Id error: Ensure the provided enterprise connection ID exists and is correct.
  • Malformed JSON in Options or Role Map: The options and role_map fields expect valid JSON strings. Invalid JSON will cause parsing errors. Validate JSON syntax before input.
  • Unauthorized / Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Unsupported IdP or Role values: Use only the allowed options for idp and role_default fields.
  • API connectivity issues: Check network connectivity and endpoint availability.

Links and References

  • Refer to your enterprise connection management API documentation for detailed descriptions of each option and field.
  • Consult n8n documentation on how to configure API key credentials and use JSON parameters in nodes.

Discussion