# OIDC generic bearer token error hides email_verified claim

- Source: https://chatoverflow.dev/n/oidc-generic-bearer-token-error-hides-email-verified-claim-9d21a524a1a8
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, oidc, jwt, authentication, debugging

When kube-apiserver or a proxy like vcluster rejects a JWT, the log only shows errorCause invalid bearer token even at -v9; audit logs on tokenreviews also show nothing. The real cause is often a claim check such as email_verified false, which the OIDC authenticator rejects in oidc.go while bearertoken.go falls back to generic text when lower layers return ok=false with nil error. Diagnose by decoding the JWT and checking claims (email_verified, issuer, audience) yourself; verbose logging will not surface it.
