feat: allow amr claim to be array of strings or objects #2274
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
This PR loosens the validation for the
amr(Authentication Method Reference) claim in custom access token hooks to accept both array of strings and array of objects, instead of only array of objects.amras an array of strings passes validationamras an array of objects still works (backward compatibility)Motivation
This change provides more flexibility for custom access token hooks. RFC-8176 requires
amrto be array of strings.Testing
All tests pass, including:
amras array of stringsamras array of objectsBackward Compatibility
Fully backward compatible - The change only adds support for an additional format. Existing hooks that return
amras an array of objects will continue to work without any changes.