> ## 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.

# Okta SSO for Kubernetes | Official Documentation

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

# Okta SSO for Kubernetes

Check the Helm information [here](https://artifacthub.io/packages/search?repo=open-metadata).

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

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

<Tabs>
  <Tab title="implicit">
    ```
    # Public Flow

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

        authentication:
          clientType: public
          provider: "okta"
          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
          - "{ISSUER_URL}/v1/keys"
          authority: "{ISSUER_URL}"
          clientId: "{Client ID}"                 # Update your Client ID
          callbackUrl: "http://localhost:8585/callback"
    ```
  </Tab>

  <Tab title="authcode">
    ```
    # Auth Code Flow

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

        authentication:
          clientType: confidential
          provider: "okta"
          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
          - "{ISSUER_URL}/v1/keys"
          authority: "{ISSUER_URL}"
          clientId: "{Client ID}"                             # Update your Client ID
          callbackUrl: "http://localhost:8585/callback"
          oidcConfiguration:
            oidcType: "okta"
            clientId:
              secretRef: oidc-secrets
              secretKey: openmetadata-oidc-client-id
            clientSecret:
              secretRef: oidc-secrets
              secretKey: openmetadata-oidc-client-secret
            discoveryUri: "http://{ISSUER_URL}/.well-known/openid-configuration"      # Update your Issuer URL
            callbackUrl: http://localhost:8585/callback
            serverUrl: http://localhost:8585
    ```
  </Tab>
</Tabs>

## 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="OKTA" href="/v1.13.x/deployment/security/okta">
    Go to okta Configuration
  </Card>
</CardGroup>