SSO (OIDC)
OpenID Connect sign-in for the Wave Console: each engineer signs in with your IdP and gets a role, and the local admin stays as a way in when the IdP is down.
3 engineers log in as one shared admin, and the audit log shows only admin
kubernetes.io, Authenticating; Wave SSO Setup docs. The 3 engineers are illustrative, from the docs diagram.
"Kubernetes does not have objects which represent normal user accounts" (kubernetes.io). A console that runs in the cluster has to bring its own sign-in.
The easy answer is one shared local admin. Then there is no per-person audit, and when someone leaves, the shared password has to change (Wave SSO Setup docs).
Shared admin and OIDC with PKCE: Wave SSO Setup docs. The people, times, and roles are illustrative.
How Wave does it
- EngineerAlice, Bob, or Carol
- passwordShared adminone account, one password
- sessionConsolefull rights for everyone
- logsAudit logevery entry says admin
- Login pagea Sign in with SSO button
- redirectYour IdPOIDC, Authorization Code with PKCE
- ID tokenWavematches the verified email to a user an admin added
- roleSessionViewer, Operator, Manager, or Admin
Connect your IdP
From Wave 3.2.2, the Web Console signs in through OpenID Connect with the Authorization Code flow and PKCE. Okta, Microsoft Entra ID, Google Workspace, and Keycloak are tested.
Add each user first
SSO users are not created on first login. An admin adds each user with their email and a role: Viewer, Operator, Manager, or Admin. The first login binds to that user by email, and a verified email is required by default.
Keep a way in
The Use local admin account toggle stays on the login page when SSO is on. If the IdP is down, the local admin can still sign in.