deployment

No menu items for this category

Okta SSO for Docker

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

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

Check the more information about environment variable here.

Auth Configuration
Implicit
Authcode

``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=okta AUTHENTICATION_PUBLIC_KEYS=[{ISSUER_URL}/v1/keys, https://{your domain}/api/v1/system/config/jwks] # Update with your Issuer URL AUTHENTICATION_AUTHORITY={ISSUER_URL} # Update with your Issuer URL AUTHENTICATION_CLIENT_ID={CLIENT_ID} # Update with your Client ID AUTHENTICATION_CALLBACK_URL=http://localhost:8585/callback AUTHENTICATION_CLIENT_TYPE= public

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 and JWT Troubleshooting to ensure seamless authentication.