Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix(auth): resolve OIDC sub claim to the Nextcloud canonical UID #1357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
fix(auth): resolve OIDC sub claim to the Nextcloud canonical UID #1357
Changes from all commits
0c60447File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟢 Nit: the cache entry built just below writes
"sub": username(now the canonical UID) but spreads the rest ofpayloadthrough unchanged, sopreferred_usernamestays as the raw claim. The entry ends up internally inconsistent — two identity fields disagreeing about who the token belongs to.Harmless today, since both readers do
sub or preferred_usernameandsubwins. But it's a live trap for whoever next reads a cache entry, or adds a third reader that preferspreferred_username. Adding it to the exclusion set alongsidesubandscopecosts nothing.Uh oh!
There was an error while loading. Please reload this page.