Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Instead of implicit fallback from userinfo to top-level claims, add an explicit --header-mapping-base / HEADER_MAPPING_BASE flag (default: /userinfo) that controls which JWT claims subtree HEADER_MAPPING reads from. Set to / for top-level claims. Closes #143
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.
Summary
--header-mapping-base/HEADER_MAPPING_BASEflag (default:/userinfo) to explicitly control which JWT claims subtreeHEADER_MAPPINGreads from./to read from top-level JWT claims, which fixes header mapping for OIDC providers (e.g. Azure AD) that do not include auserinfoclaim in the JWT./,/userinfo, and missing base scenarios.--header-mappingand--header-mapping-basein the configuration reference.Type of Change
Related Issues
Closes #143