Configure OpenMetadata Helm

Update Helm Values

Once the Client Id, and Issuer URL are generated, add those details in openmetadata-security.yaml file in the respective fields.

authenticationConfiguration:
  provider: "okta"
  publicKeyUrls:
    - "{ISSUER_URL}/v1/keys"
  authority: "{ISSUER_URL}"
  clientId: "{CLIENT_ID - SPA APP}"
  callbackUrl: "http://localhost:8585/callback"

ISSUER_URL - This can be found in Security -> API -> Authorization Servers.

CLIENT_ID - SPA APP - This is the Client_ID for Single Page Applications. On configuring the app, the Client_ID can be found in the General section, under Client Credentials >> Client ID

Update authorizerConfiguration to add adminPrincipals

For adminPrincipals, add the Username.
For botPrincipals, add the Ingestion Client ID for the Service application. This can be found in Okta -> Applications -> Applications.

global:
  authorizer:
    className: "org.openmetadata.catalog.security.DefaultAuthorizer"
    containerRequestFilter: "org.openmetadata.catalog.security.JwtFilter"
    initialAdmin: "<username>"
    botPrincipal: "<Ingestion Client ID>"
    principalDomain: "open-metadata.org"
  authentication:
    provider: "okta"
    publicKey: "{ISSUER_URL}/v1/keys"
    authority: "{ISSUER_URL}"
    clientId: "{CLIENT_ID - SPA APP}"
    callbackUrl: "http://localhost:8585/callback"
authenticationConfiguration:
  provider: "okta"
  publicKey: "{ISSUER_URL}/v1/keys"
  authority: "{ISSUER_URL}"
  clientId: "{CLIENT_ID - SPA APP}"
  callbackUrl: "http://localhost:8585/callback"

Upgrade Helm Release

Head towards upgrade-openmetadata-on-kubernetes.md to upgrade your OpenMetadata Helm Release.

2.0 KiB Raw Blame History

Configure OpenMetadata Helm

Update Helm Values

Upgrade Helm Release

2.0 KiB

Raw Blame History