Repository navigation
fix(auth): take JWT sys_admin/support from the user record - #459
Merged
Merged
Conversation
The user record now decides permissions for bearer JWTs, rather than only capping the token's claims, so a promotion also applies to existing sessions without the user signing in again. API keys keep their own stored permissions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow-up to 8779928.
Summary
sys_admin/supportnow come from the user record, and the token's claims are ignored. Before, the record only capped the claims. Now a promotion also applies to existing sessions without the user signing in again, and a demotion still applies straight away.Tests
spec/live_permissions_spec.cr: the promotion case now expects the same token to gain admin and support access.🤖 Generated with Claude Code