feat: merge string claims across scopes instead of erroring - #1
Merged
Conversation
When multiple requested scopes define the same string-typed claim key, concatenate the values space-separated rather than returning a conflict error. Non-string conflicts still error. Also adds path/body scope mismatch validation in the update handler, fixes bearer token parsing, adds e2e CI job, multi-arch image builds, and scope-merge e2e test. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
paullatzelsperger
force-pushed
the
fix/scope_merge
branch
from
June 3, 2026 08:16
55055f9 to
a9fa489
Compare
wolf4ood
approved these changes
Jun 4, 2026
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
2 participants
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.
Summary
update_scope_mappinghandler.strip_prefixdirectly instead of a lowercase conversion that discarded the original case.