> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open-metadata.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure SSO | OpenMetadata Security Integration

> Configure Auth0 inside Docker containers to manage secure user logins with backend token validation and low-latency identity workflows.

# Auth0 SSO for Docker

To enable security for the Docker deployment, follow the next steps:

## 1. Create an .env file

Create an `openmetadata_auth0.env` file and use the following example as a reference. Replace the placeholder values with the details generated during your Auth0 account and application credentials setup.

Check the more information about environment variable [here](/v1.12.x/deployment/security/configuration-parameters).

<Tabs>
  <Tab title="implicit">
    ```
    # Implicit Flow
    AUTHORIZER_CLASS_NAME=org.openmetadata.service.security.DefaultAuthorizer
    AUTHORIZER_REQUEST_FILTER=org.openmetadata.service.security.JwtFilter
    AUTHORIZER_ADMIN_PRINCIPALS=[admin]                 # john.doe from john.doe@example.com
    AUTHORIZER_PRINCIPAL_DOMAIN=open-metadata.org       # Update with your Domain,The primary domain for the organization (example.com from john.doe@example.com).
    AUTHENTICATION_PROVIDER=auth0
    AUTHENTICATION_PUBLIC_KEYS=[{Domain}/.well-known/jwks.json, https://{your domain}/api/v1/system/config/jwks]     # Update with your Domain and Make sure this "/api/v1/system/config/jwks" is always configured to enable JWT tokens
    AUTHENTICATION_AUTHORITY={Domain}                   # The base URL of the authentication provider.
    AUTHENTICATION_CLIENT_ID={Client ID}                # Update with your Client ID
    AUTHENTICATION_CALLBACK_URL=http://localhost:8585/callback
    AUTHENTICATION_CLIENT_TYPE= public
    ```
  </Tab>

  <Tab title="authcode">
    ```
    # Auth Code Flow
    AUTHORIZER_CLASS_NAME=org.openmetadata.service.security.DefaultAuthorizer
    AUTHORIZER_REQUEST_FILTER=org.openmetadata.service.security.JwtFilter
    AUTHORIZER_ADMIN_PRINCIPALS=[admin]                 # john.doe from john.doe@example.com
    AUTHORIZER_PRINCIPAL_DOMAIN=open-metadata.org       # Update with your Domain,The primary domain for the organization (example.com from john.doe@example.com).
    AUTHENTICATION_PROVIDER=auth0
    AUTHENTICATION_PUBLIC_KEYS=[{Domain}/.well-known/jwks.json, https://{your domain}/api/v1/system/config/jwks]         # Update with your Domain and Make sure this "/api/v1/system/config/jwks" is always configured to enable JWT tokens
    AUTHENTICATION_AUTHORITY={Domain}                   # The base URL of the authentication provider.
    AUTHENTICATION_CLIENT_ID={Client ID}                # Update with your Client ID
    AUTHENTICATION_CALLBACK_URL=http://localhost:8585/callback
    AUTHENTICATION_CLIENT_TYPE= confidential

    OIDC_CLIENT_ID={Client ID}                          # Update with your Client ID
    OIDC_TYPE=auth0
    OIDC_CLIENT_SECRET={Client Secret}                  # Update with your Client Secret
    OIDC_DISCOVERY_URI: http://{Domain}/.well-known/openid-configuration        # Update with your Domain
    OIDC_CALLBACK: ${OIDC_CALLBACK:-"http://localhost:8585/callback"}


    ```
  </Tab>
</Tabs>

## 2. Start Docker

```commandline theme={null}
docker compose --env-file ~/openmetadata_auth0.env up -d
```

## Configure Ingestion

Once your server security is set, it's time to review the ingestion configuration. Our bots support JWT tokens
to authenticate to the server when sending requests.

Find more information on [**Enabling JWT Tokens**](/deployment/security/enable-jwt-tokens) and [**JWT Troubleshooting**](/deployment/security/jwt-troubleshooting) to ensure seamless authentication.

<CardGroup cols={1}>
  <Card title="Auth" href="/v1.12.x/deployment/security/auth0">
    Go to Auth0 Configuration
  </Card>
</CardGroup>