2.6 KiB
| title | slug | collate |
|---|---|---|
| Auth0 SSO | /deployment/security/auth0 | false |
Auth0 SSO
Follow the sections in this guide to set up Auth0 SSO.
{%important%}
Security requirements for your production environment:
- DELETE the admin default account shipped by OM in case you had Basic Authentication enabled before configuring the authentication with Auth0 SSO.
- UPDATE the Private / Public keys used for the JWT Tokens. The keys we provide by default are aimed only for quickstart and testing purposes. They should NEVER be used in a production installation.
{%/important%}
Create Server Credentials
Step 1: Create the Account
- If you don't have an account, Sign up to create one.
- Select the Account Type, i.e., Company or Personal
- Click I need advanced settings and click next.
{% image src="/images/v1.6/deployment/security/auth0/create-account-1.png" alt="create-account" /%}
- Provide the Tenant Domain, select the region and click on Create Account.
{% image src="/images/v1.6/deployment/security/auth0/create-account-2.png" alt="create-account" /%}
- Once done, you will land on the dashboard page.
{% image src="/images/v1.6/deployment/security/auth0/create-account-3.png" alt="create-account" /%}
Step 2: Create Server Credentials
Choose Your Authentication Flow
After creating the account, choose the authentication flow you want to use:
- Implicit Flow (Public)
- Auth Code Flow (Confidential)
{% note %}
-
SPA (Single Page Application):
This type is designed for implicit flows. In this case, providing both the client ID and client secret will result in a failure because the implicit flow only requires the client ID for authentication. -
Web:
This type is intended for confidential clients. If you select this option, you must provide both the client ID and client secret. Simply passing the client ID will cause the authorization process to fail, as the Authorization Code flow requires both credentials for successful authentication. The OIDC Authorization Code Flow is used in this case, where the client secret is required to securely exchange the authorization code for tokens.
Recommendation:
- Use the Web type for confidential clients that require both a client ID and secret.
- Use the SPA type for applications using implicit flows where only a client ID is needed.
{% /note %}
{% partial file="/v1.6/deployment/configure-ingestion.md" /%}