{{ message }}
Repository navigation
docs: Clarify identity header propagation in NGINX Ingress - #3564
Open
Sahvendra7 wants to merge 1 commit into
Open
Sahvendra7 wants to merge 1 commit into
Sahvendra7 wants to merge 1 commit into
Conversation
Contributor
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Needs approval from an approver in each of these files:Approvers can indicate their approval by writing |
Author
This adds a section explaining how to properly propagate identity headers when using OAuth2-Proxy in auth-url (Forward Auth) mode with NGINX Ingress, specifically noting the architectural difference between `--pass-user-headers` and `--set-xauthrequest`. Fixes oauth2-proxy#3127 Signed-off-by: Sahvendra <shyamajanidhaka@gmail.com>
Sahvendra7
force-pushed
the
docs/nginx-ingress-headers
branch
from
October 7, 2026 12:04
02b3a47 to
9df68c4
Compare
This branch has not been deployed
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.
This adds a section explaining how to properly propagate identity headers when using OAuth2-Proxy in
auth-url(Forward Auth) mode with NGINX Ingress. It specifically notes the architectural difference between--pass-user-headersand--set-xauthrequest.