Azure SSO for Kubernetes | Official Documentation

Connect Kubernetes to enable streamlined access, monitoring, or search of enterprise data using secure and scalable integrations.

Azure SSO for Kubernetes

Check the Helm information here.

Check the more information about environment variable here.

Here is an example for reference, showing where to place the values in the values.yaml file after setting up your Azure account and obtaining the application credentials.

implicit

# Public Flow

openmetadata:
  config:
    authorizer:
      className: "org.openmetadata.service.security.DefaultAuthorizer"
      containerRequestFilter: "org.openmetadata.service.security.JwtFilter"
      initialAdmins:  # john.doe from [e-mail]
      - "admin"
      - "user1"
      - "user2"
      principalDomain: "open-metadata.org"  # Update with your Domain,The primary domain for the organization (example.com from [e-mail]).

    authentication:
      clientType: public
      provider: "azure"
      publicKeys:
      - "{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
      - "https://login.microsoftonline.com/common/discovery/keys"
      authority: "https://login.microsoftonline.com/{Tenant ID}"     # Update your Tenant ID
      clientId: "{Client ID}"                                        # Update your Client ID
      callbackUrl: "http://localhost:8585/callback"

authcode

# Auth Code Flow

openmetadata:
  config:
    authorizer:
      className: "org.openmetadata.service.security.DefaultAuthorizer"
      containerRequestFilter: "org.openmetadata.service.security.JwtFilter"
      initialAdmins:  # john.doe from [e-mail]
      - "admin"
      - "user1"
      - "user2"
      principalDomain: "open-metadata.org"  # Update with your Domain,The primary domain for the organization (example.com from [e-mail]).

    authentication:
      clientType: confidential
      provider: "azure"
      publicKeys:
      - "{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
      - "https://login.microsoftonline.com/common/discovery/keys"
      authority: "https://login.microsoftonline.com/{Tenant ID}"    # Update your Tenant ID
      clientId: "{Client ID}"                                       # Update your Client ID
      callbackUrl: "http://localhost:8585/callback"
      oidcConfiguration:
        oidcType: "azure"
        oidcConfiguration.enabled: true
        clientId:
          secretRef: oidc-secrets
          secretKey: openmetadata-oidc-client-id
        clientSecret:
          secretRef: oidc-secrets
          secretKey: openmetadata-oidc-client-secret
        discoveryUri: "https://login.microsoftonline.com/.well-known/openid-configuration"
        callbackUrl: http://localhost:8585/callback
        serverUrl: http://localhost:8585

Altering the order of claims in jwtPrincipalClaims may lead to problems when matching a user from a token with an existing user in the system. The mapping process relies on the specific order of claims, so changing it can result in inconsistencies or authentication failures, as the system cannot ensure correct user mapping with a new claim order.

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

Azure

Go to Azure Configuration