feat: forward authenticated user identity to upstream via headers#135
Merged
feat: forward authenticated user identity to upstream via headers#135
Conversation
Add --header-mapping flag to inject OIDC/Google/GitHub userinfo attributes into upstream request headers. Userinfo is embedded as JWT custom claims and extracted in the proxy using JSON pointers. Also fixes JWT subject claim from hardcoded "user" to the actual authenticated user's identity. Closes #130
Integrate GrantAudience, trailing-slash normalization, healthz endpoint, and state-generation changes from main while preserving header-mapping feature additions.
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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-mappingflag (HEADER_MAPPINGenv var) to inject authenticated user identity into upstream request headers by mapping userinfo fields via JSON pointers (e.g.,/email:X-Forwarded-Email)"user"to the actual authenticated user's identityType of Change
Related Issues
Closes #130