Configure DataStax Mission Control to use OpenID Connect (OIDC) for authentication
DataStax Mission Control is currently in Public Preview. DataStax Mission Control is not intended for production use, has not been certified for production workloads, and might contain bugs and other functional issues. There is no guarantee that DataStax Mission Control will ever become generally available. DataStax Mission Control is provided on an “AS IS” basis, without warranty or indemnity of any kind.
If you are interested in trying out DataStax Mission Control please join the Public Preview.
DataStax Mission Control can use the OpenID Connect (OIDC) or LDAP protocols for authentication. This topic describes configuring the OpenID Connect setup. See Configure DataStax Mission Control to use LDAP for the other supported authentication protocol.
kubectlCLI tool, v1.22 or later.
An instance of DataStax Mission Control, installed through either your own Kubernetes cluster or the runtime installer. See planning for your installation.
kubectlplugin installed with this command:
`curl -sSL https://kots.io/install | bash`
Kubernetes contextpointing to the DataStax Mission Control cluster running the DataStax Mission Control
Control Plane. Set this up with the following command:
kubectl config current-context
Port-forward to the admin console:
kubectl kots admin-console
Navigate to http://127.0.0.1:8800 (password admin) and edit the Mission Control configuration to enable the OIDC connector. Fill in the
connectorsections by providing your environment’s OIDC information.
Deploy the new configuration.
Navigate to the DataStax Mission Control UI and try to connect with OIDC.
You can also remove the admin user in the Mission Control configuration, and the
connect with emailoption should no longer be available.