You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 12, 2024. It is now read-only.
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
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:
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
The text was updated successfully, but these errors were encountered: