Skip to content
This repository has been archived by the owner on Jun 12, 2024. It is now read-only.

Reverse Proxy Authentication #900

Open
1 of 3 tasks
hodosyp opened this issue May 18, 2024 · 0 comments
Open
1 of 3 tasks

Reverse Proxy Authentication #900

hodosyp opened this issue May 18, 2024 · 0 comments

Comments

@hodosyp
Copy link

hodosyp commented May 18, 2024

What is the problem you are trying to solve with this feature?

I am using my services (like Homebox) behind a reverse proxy. In the proxy I already have custom authentication solution like Auth in LDAP or mTLS. I would like to use the reverse proxy Authentication solution and bypass the Homebox one.

What is the solution you are proposing?

I would like to have a new Authentication Provider which:

  • Reads a certain header for username
  • Doesn't care about password and makes the forwarded user always logged in
  • Can use the registered users list (optional)
  • The auth provider can be set via Docker Environment variable

Similar solution in Gitea Reverse Proxy

What alternatives have you considered?

No Auth. A possibility to have one global user (Anonymous) who is always logged in. For home use this would work as well.

Additional context

No response

Contributions

  • I have searched through existing issues and feature requests to see if my idea has already been proposed.
  • If this feature is accepted, I would be willing to help implement and maintain this feature.
  • If this feature is accepted, I'm willing to sponsor the development of this feature.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant