Authentication

Manage Redis Software cluster credentials, LDAP, SSO, and configuration secrets on Kubernetes.

Authentication covers cluster credentials, external identity providers (LDAP and SAML SSO), and configuration secrets. The operator generates the initial cluster admin credentials, applies LDAP and SSO settings from the RedisEnterpriseCluster spec, and reads configuration values from Kubernetes Secrets you can update without a cluster restart.

How authentication works on Redis for Kubernetes

• Cluster credentials are auto-generated at install and stored in a Kubernetes Secret named after the REC resource. Retrieve and update them with kubectl.
• LDAP is configured on the RedisEnterpriseCluster spec. The operator applies the configuration through the Redis Software REST API.
• SAML SSO is enabled on the REC spec. The operator configures the identity provider connection in Redis Software.
• Configuration secrets let you store sensitive configuration items in Kubernetes Secrets that the operator references. Updates to the Secret reconcile automatically.

What's the same as Redis Software

The underlying Redis Software behavior is unchanged. For concepts and reference details, see the existing Redis Software docs:

• LDAP authentication overview — server requirements, supported attributes, and the LDAP model.
• Enable role-based LDAP — concepts behind role-based LDAP.
• Map LDAP groups to roles — group-to-role mapping rules.
• SAML single sign-on — identity provider requirements and SAML attribute mappings.
• Default user — what the bootstrap admin account is for.

What's different on Kubernetes

• Initial credentials are auto-generated by default. If you don't provide them, the operator generates them and stores them in the credentials Secret, which you retrieve after the REC is up. You can instead supply your own Secret name and credentials at cluster creation time.
• Change the cluster admin credentials in Redis Software, then mirror them to the Secret. Update the credentials directly in Redis Software and reflect the new values in the credentials Secret — see Manage REC credentials. Credentials for other users are managed through their RedisEnterpriseUser resources and Secrets.
• LDAP and SSO configuration is part of the REC spec. The operator applies it through the Redis Software REST API, so the configuration is source-controlled.
• Sensitive values live in Kubernetes Secrets (or HashiCorp Vault) instead of in Redis Software configuration files.

In this section

• Manage REC credentials — retrieve and update the cluster admin credentials Secret.
• Manage REDB passwords — retrieve and rotate database passwords through the database Secret.
• Configuration secrets — store config items in Kubernetes Secrets and reconcile updates automatically.
• LDAP authentication — configure LDAP for Cluster Manager and database access.
• SSO authentication — configure SAML single sign-on for the Cluster Manager UI.