2.1 KiB
title | slug |
---|---|
Auth0 SSO for Kubernetes | /deployment/security/auth0/kubernetes |
Auth0 SSO for Kubernetes
Check the Helm information here.
Once the Client Id
and Client Secret
are generated, see the snippet below for an example of where to
place the client id value and update the authorizer configurations in the values.yaml
.
-
Update
initialAdmins
Make sure you configure the name from email, example: xyz@helloworld.com, initialAdmins username will bexyz
-
Update the
principalDomain
to your company domain name. Example from above, principalDomain should behelloworld.com
{% note noteType="Warning" %}
It is important to leave the publicKeys configuration to have both Auth0 public keys URL and OpenMetadata public keys URL.
- Auth0 Public Keys are used to authenticate User's login
- OpenMetadata JWT keys are used to authenticate Bot's login
- Important to update the URLs documented in below configuration. The below config reflects a setup where all dependencies are hosted in a single host. Example openmetadata:8585 might not be the same domain you may be using in your installation.
- OpenMetadata ships default public/private key, These must be changed in your production deployment to avoid any security issues.
For more details, follow Enabling JWT Authenticaiton
{% /note %}
global:
authorizer:
className: "org.openmetadata.service.security.DefaultAuthorizer"
containerRequestFilter: "org.openmetadata.service.security.JwtFilter"
initialAdmins:
- "admin"
principalDomain: "open-metadata.org"
authentication:
provider: "auth0"
publicKeys:
- "http://openmetadata:8585/api/v1/system/config/jwks"
- "{Auth0 Domain Name}/.well-known/jwks.json"
authority: "https://parth-panchal.us.auth0.com/"
clientId: "{Client ID}"
callbackUrl: "http://localhost:8585/callback"
{% note noteType="Tip" %}
Follow this guide to configure the ingestion-bot
credentials for ingesting data using Connectors.
{% /note %}