Auth0

The Auth0 Connector provides a way for Maverics to interact with an Auth0 organization. The Connector uses the Auth0 User API to create users or query for attributes and OpenID Connect to authenticate users and perform session validation.

Configuration options

The following values can be provided to the Auth0 Connector via the Maverics configuration file.

OAuth Client ID

oauthClientID is the client ID of the Maverics application registered in the Auth0 organization.

OAuth Client Secret

oauthClientSecret is the client secret of the Maverics application registered in the Auth0 organization.

OAuth Login Redirect

oauthLoginRedirect is used to define login redirect callback URLs.

It defines the urls that the OIDC provider will use to redirect the client back to after authentication. The urls must be absolute URLs and match exactly with one of the registered URLs on the provider. If no matches are found during the auth flow, the first URL from the urls list will be used.

The orchestrator will serve the callback handlers on all URLs specified in the urls field under this section.

ℹ️

The urls paths should not conflict with the path of any application resources. The path can be arbitrary (e.g. /maverics-oidc or /oidc-handler).

OIDC Well-known URL

oidcWellKnownURL is the URL that returns OpenID Connect metadata about the Auth0 authorization server.

Logout URL

logoutURL is Auth0’s application logout URL that will initiate logout in Auth0. This will invalidate the SSO cookie in Auth0 but the cookie will still remain in the browser.

OAuth Logout Redirect

oauthLogoutRedirect is used to define urls that an OIDC provider will use to redirect the client back to the application after logging out the user.

The urls must be absolute URLs and match exactly with one of the registered URLs on the provider. If no matches are found during the logout flow, the first URL from the urls list will be used.

The orchestrator will serve the callback handlers on all URLs specified in the urls field under this section.

ℹ️

The urls paths should not conflict with the path of any application resources. The path can be arbitrary (e.g. /oidc-logout or /logout-handler).

Disable PKCE

disablePKCE disables the Proof Key for Code Exchange (PKCE) extension (enabled by default).

Error Page

errorPage is the page presented to the user if an error occurs.

Domain

domain is the tenant’s Auth0 domain in full URL format. For example, https://yourtenant.us.auth0.com. This field is only required when interacting with Auth0 API to query user attributes.

Health Check

healthCheck defines an optional health check for the connector. This option is required when using the connector in an IDP-continuity scenario. For more info on how to define the health check, please see the docs.

Examples

OIDC Configuration

connectors:
  - name: auth0-example
    type: auth0
    oidcWellKnownURL: https://yourtenant.us.auth0.com/.well-known/openid-configuration
    oauthLoginRedirect:
      urls:
        - https://host1.example.com/oidc
        - https://host2.example.com/oidc
    oauthLogoutRedirect:
      urls:
        - https://host1.example.com/logout
        - https://host2.example.com/logout
    oauthClientID: <auth0-client-id>
    oauthClientSecret: <auth0-client-secret>
    logoutURL: https://yourtenant.us.auth0.com/v2/logout

Amazon Cognito Connector Health Checks