Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support forwarded headers with external auth #10949

Open
arsnyder16 opened this issue Jan 31, 2024 · 2 comments
Open

Support forwarded headers with external auth #10949

arsnyder16 opened this issue Jan 31, 2024 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@arsnyder16
Copy link

arsnyder16 commented Jan 31, 2024

A way to allow forwarded headers to be passed to external auth configured with auth-url.

Currently when using auth-url despite the values of use-forwarded-headers and compute-full-forwarded-for only x-forwarded-for is sent to the external auth service. x-forward-proto, x-forwarded-scheme etc are stripped. Another set of configurations similar to use-forwarded-headers and compute-full-forwarded-for that apply to just the external auth would be desirable.

Currently a work around is to use auth-proxy-set-headers and hardcode any value, but this has it limitations since it isn't dynamic

@arsnyder16 arsnyder16 added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 31, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Jan 31, 2024
Copy link

github-actions bot commented Mar 2, 2024

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

@github-actions github-actions bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Development

No branches or pull requests

2 participants