PricingPricingDocsDocsBlogBlogBook a demoBook a demoCompanyCompany (opens in a new tab)
Product
DocsAPI ReferencePricingConsole DemoBlogCompany
Start Freev3.4.7
Platform & Observability

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.

The challenge

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

Three people as one admin, then three people with their own namesWithout WaveWith Waveadminalicebobcarol3 people, 1 name3 people, 3 names
Without Wave
One shared admin: every log row says adminAliceBobCaroladminshared passwordWave ConsoleAudit log10:02 admin10:15 admin10:31 admin
3 engineers, Alice, Bob, and Carol, sign in as one shared admin. The log cannot tell them apart, and when one of them leaves, the password has to change.
With Wave
Each engineer signs in through the IdPAliceBobCarolOIDC IdPCode + PKCEWave ConsoleAudit log10:02 alice Operator10:15 bob Viewer10:31 carol Admin
The same 3 engineers sign in through the company IdP. Each row in the log has a name and the role an admin gave that person.

Shared admin and OIDC with PKCE: Wave SSO Setup docs. The people, times, and roles are illustrative.

How Wave does it

From one shared login to a name on every change
Shared local adminWho changed it: unknown
  1. Engineer
    Alice, Bob, or Carol
  2. ↓password→
    Shared admin
    one account, one password
  3. ↓session→
    Console
    full rights for everyone
  4. ↓logs→
    Audit log
    every entry says admin
Wave SSOEach login has a name
  1. Login page
    a Sign in with SSO button
  2. ↓redirect→
    Your IdP
    OIDC, Authorization Code with PKCE
  3. ↓ID token→
    Wave
    matches the verified email to a user an admin added
  4. ↓role→
    Session
    Viewer, Operator, Manager, or Admin
Default lane: kubernetes.io (Authenticating) and the Wave SSO Setup docs (shared local admin). Wave lane: Wave SSO Setup docs.
1

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.

2

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.

3

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.

Related in Platform & Observability

Programmable API →PV Auto-Expansion →PV Cleanup →Alerts →Cluster Map →Prometheus & Grafana Integration →Read the docs →
Book a demoStart free
Product
Wave GPUAI Infrastructure Professional ServiceWaveWave AI Agent2026 Q4
Resources
DocsAPI ReferenceBlogConsole DemoPricing
Company
STCLabBook a demoContact
STCLab© 2026 Wave All rights reserved.
Terms of ServicePrivacy PolicyCookies