-
Notifications
You must be signed in to change notification settings - Fork 3k
Adding oidc and/or header authenticatiom #1387
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
Comments
See #1388 Closing this, please continue discussions on the PR. |
I didn't think of authenticating proxy hosts using oidc, but the UI itself. Can this PR be used for that? |
I'll say no. However you could create a proxy host for the admin interface and put it behind oidc but then you'll also need to log in to the ui after oidc.. also I think the Alternative UI authentication options won't be added to v2. They can be considered for v3, though the list of features to add for that is already huge. |
Could you please add it in v3 or point me to how to contribute and make it happen? |
I also use Authelia and would love a Proxy/Header Authentication. Could we set some kind of a bounty for this feature. I would be willing to pay for this. |
Is your feature request related to a problem? Please describe.
I have Authelia setup as my SSO, and I authenticate there and then I am forwarded to NPM login page and if I am not at my computer can't log in considering I have a strong password,
Describe the solution you'd like
Adding support for oidc to authenticate and/or header auth considering NPM is already proxied by itself.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: