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 Request: Add support for authentication by reverse proxy #152

Open
max-tet opened this issue Mar 20, 2021 · 1 comment
Open

Feature Request: Add support for authentication by reverse proxy #152

max-tet opened this issue Mar 20, 2021 · 1 comment
Labels
Enhancement New feature or request

Comments

@max-tet
Copy link

max-tet commented Mar 20, 2021

Summary:
Add configuration options: 1) enable proxy auth, 2) proxy auth http-header (e.g. X-Authenticated-User).

If proxy auth is enabled, user login is bypassed and the user that is present in the specified header is used.

Optional: if no such user exists, automatically create one.

How important this is to me and why:
Some on-premise hosting approaches put everything behind a reverse proxy like Traefik and let authentication be handled there. See e.g. here. This feature would enable this kind of deployment.

Importance: High - because it might be really easy and therefore a quick win.

Use cases:

  1. on-premise hosting with reverse-proxy auth
  2. personal self-hosting

Additional context / similar features:
Example: Filebrowser

Thanks a lot, cheers!

@p-baum
Copy link

p-baum commented May 29, 2022

The broken link above should be https://doc.traefik.io/traefik/middlewares/http/forwardauth/

I would also be very pleased to see this implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants