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

Feature: Passthrough Proxy-Authorization header #10366

Open
2 tasks done
voruti opened this issue Jan 21, 2024 · 1 comment
Open
2 tasks done

Feature: Passthrough Proxy-Authorization header #10366

voruti opened this issue Jan 21, 2024 · 1 comment
Labels
area/server kind/proposal a proposal that needs to be discussed.

Comments

@voruti
Copy link

voruti commented Jan 21, 2024

Welcome!

  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?

As already discussed in the forum I would like to pass-through the Proxy-Authorization header to a service behind Traefik.

Since #7374 it's already possible to use it for a service behind the forwardauth middleware. In my use case (authelia/authelia#6542 (reply in thread), Host 1 in the image) I have an authorization server not only behind the forwardauth middleware, but also as a direct backend service behind Traefik.

I already did some research on my own (on why the header currently is removed, what would need to be done, etc. - see forum link above), but ultimately I don't know enough about the subject.

@lbenguigui
Copy link
Contributor

Hello @voruti,

Thanks for your suggestion.

We are interested in this issue, but we’re unsure about the use case and the traction it will receive. We are going to leave the status as kind/proposal to give the community time to let us know if they would like this idea.
We will reevaluate as people respond.

If you or another community member would like to build it before that happens, let us know, and we will work with you to make sure you have all the information needed.

Let us know here before you start. We prefer to work with our community members at the beginning of the design process to ensure that we are aligned and can move quickly with the review and merge process.

@lbenguigui lbenguigui added kind/proposal a proposal that needs to be discussed. and removed status/0-needs-triage labels Jan 25, 2024
@lbenguigui lbenguigui removed their assignment Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/server kind/proposal a proposal that needs to be discussed.
Projects
None yet
Development

No branches or pull requests

4 participants