mirror of
https://github.com/pocket-id/pocket-id.git
synced 2025-12-06 09:13:19 +03:00
🐛 Bug Report: initial id token contains groups claim but subsequent tokens generated using refresh token don't
#11
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @michaelbeaumont on GitHub.
Reproduction steps
NOTE: this started happening with v1.11
When I use
kube oidc-loginwith--oidc-extra-scope=groupsagainst pocket-id and don't yet have a token, it calls/authorize?access_type=offline...and gets an id token that contains my groups, along with a refresh token. The k8s API server authorizes me using thegroupsclaim. When that id_token expires andkubectl oidc-logintries to get a new one, the new id token doesn't contain my groups and authorization fails.NOTE: this has nothing to do with Kubernetes. I can verify locally that the id token does not contain the groups.
Expected behavior
Later id tokens generated with a refresh token also contain the
groupsclaim.Actual Behavior
Later id tokens generated with a refresh token don't contain the
groupsclaim.Pocket ID Version
v1.11.2
Database
SQLite
OS and Environment
On GCP using v1.12.2-distroless
Log Output
No response
@ItalyPaleAle commented on GitHub:
Fixed in #989 thanks for the report