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.

Sign up for GitHub

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

Jump to bottom

Write authenticated user to header key #802

Closed
ViViDboarder opened this issue Nov 4, 2016 · 1 comment · Fixed by #889
Closed

Write authenticated user to header key #802

ViViDboarder opened this issue Nov 4, 2016 · 1 comment · Fixed by #889
Labels
kind/enhancement a new or improved feature. status/5-frozen-due-to-age

Comments

@ViViDboarder
Copy link
Contributor

The new backend auth is pretty useful to block access to a website that doesn't provide any out of the box authentication. It would be even more useful if there was a way to write the authenticated user to a header so that the application could identify the user.

It would be great to use this sort of proxy auth with services like Gogs or Grafana that support allowing your proxy to authenticate for you and then pass the identity across.

I can take a crack at it myself, but could use some pointing in the right direction. Is this the right direction? https://blog.raintank.io/authproxy-howto-use-external-authentication-handlers-with-grafana/
@errm errm added the kind/enhancement a new or improved feature. label Nov 10, 2016
@ViViDboarder
Copy link
Contributor Author

@emilevauge any idea if this would be accepted and, if so, where I should look to implement?

Happy to go at it myself! Thanks!

ViViDboarder added a commit to ViViDboarder/traefik that referenced this issue Nov 23, 2016
@ViViDboarder
Add ability to set authenticated user in request header
0cf16c7 
Some web applications provide the ability to authorize users based on
the authenticated from Basic Auth. This patch provides a way to set a
key to which the authenticated user can be set in the Header.

For example, if I set `HeaderValue = "X-WebAuth-User"` and authenticate,
my application will be able to read my user name from that header and
provide me with the proper access.

This fixes traefik#802
@ViViDboarder ViViDboarder mentioned this issue Nov 23, 2016
Merged
emilevauge pushed a commit that referenced this issue Dec 16, 2016
@ViViDboarder @emilevauge
Add ability to set authenticated user in request header (#889)
94bb7a1 
* Add ability to set authenticated user in request header

Some web applications provide the ability to authorize users based on
the authenticated from Basic Auth. This patch provides a way to set a
key to which the authenticated user can be set in the Header.

For example, if I set `HeaderValue = "X-WebAuth-User"` and authenticate,
my application will be able to read my user name from that header and
provide me with the proper access.

This fixes #802
@traefik traefik locked and limited conversation to collaborators Sep 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/enhancement a new or improved feature. status/5-frozen-due-to-age
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add ability to set authenticated user in request header ViViDboarder/traefik
3 participants
@errm @ViViDboarder @traefiker