Configure Mission Control to use OpenID Connect (OIDC) for authentication

Mission Control can use the OpenID Connect (OIDC) or Lightweight Directory Access Protocol (LDAP) protocols for authentication. This topic explains how to configure the OIDC setup. See Configure Mission Control to use LDAP for the other supported authentication protocol.

Prerequisites

An instance of Mission Control, installed on your own Kubernetes cluster. See plan your installation.
A prepared Mission Control environment on an existing Kubernetes cluster
Reference the OIDC configuration, connector fields and values information.

Enable OIDC

Configure the OIDC connector in your values.yaml file under the dex section:

dex:
  config:
    connectors:
      - type: oidc
        id: oidc
        name: OpenID Connect
        config:
          # Add your OIDC configuration here

See the Dex OIDC connector documentation for available fields and their descriptions.

Apply the updated configuration:

helm upgrade mission-control ./mission-control -f values.yaml

Navigate to the Mission Control UI, and then click Sign in with OpenID Connect to test the connection.
Optional: Remove the admin user in the Mission Control configuration to remove the Sign in with Email option.

Configure Mission Control to use OpenID Connect (OIDC) for authentication

Prerequisites

Enable OIDC

Was this helpful?

Give Feedback