AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation allows users to create a new Enterprise Connection within an organization. Enterprise Connections typically represent integrations with external identity providers (IDPs) or authentication strategies that enable single sign-on (SSO) or centralized user management for an organization.

Common scenarios where this node is beneficial include:

  • Automating the setup of SSO connections for organizations using OIDC or other supported IDP strategies.
  • Managing enterprise authentication configurations programmatically as part of onboarding or infrastructure-as-code workflows.
  • Creating customized role mappings and default roles for users authenticated via the enterprise connection.

For example, an admin could use this node to create an OIDC-based enterprise connection for a specific organization, specifying options such as the IDP type (e.g., Okta, Azure), default user roles, and display names.

Properties

Name Meaning
Organization Id The numeric identifier of the organization under which the enterprise connection will be created.
Strategy The authentication strategy for the enterprise connection. Currently supports only "Oidc" (OpenID Connect).
Options A JSON object containing strategy-specific configuration options for the enterprise connection. The exact attributes depend on the chosen strategy and should be provided accordingly.
Additional Body Fields Optional additional fields to customize the enterprise connection:
- Default Organization Id: Numeric ID for a default organization.
- Display Name: UI-visible name for the connection; defaults to strategy if blank.
- Role Default: Default user role assigned; options include Administrator, Read Only, Owner, Technical, Accountant, Policies Only, Super Administrator.
- Role Map: JSON array defining custom role mappings.
- Idp: Type of the identity provider; options include Openid, Okta, Azure, Google.

Output

The node outputs JSON data representing the newly created enterprise connection resource. This output typically includes details such as the connection's unique ID, associated organization, strategy, configured options, display name, roles, and IDP information.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating requests to the backend service managing enterprise connections.
  • The node sends HTTP requests with JSON bodies to the relevant API endpoint.
  • No additional external dependencies are indicated in the source code.

Troubleshooting

  • Invalid Organization Id: Ensure the organization ID provided exists and is accessible by the authenticated user.
  • Malformed JSON in Options or Role Map: The options and role_map properties expect valid JSON strings. Invalid JSON will cause parsing errors. Validate JSON syntax before input.
  • Unsupported Strategy or Idp: Currently, only the "oidc" strategy is supported. Using unsupported values may result in errors.
  • Missing Required Fields: Organization Id, Strategy, and Options are required. Omitting these will cause request failures.
  • API Authentication Errors: Verify that the API key credential is correctly configured and has sufficient permissions.

Links and References

  • OpenID Connect (OIDC) Specification
  • Documentation for your backend API managing enterprise connections (not provided here)
  • n8n documentation on creating custom nodes and handling JSON inputs

Discussion