-
-
Notifications
You must be signed in to change notification settings - Fork 246
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] Allow to disable default password log in after SSO is configured #406
Labels
feature request
New feature or request
Comments
Maybe the |
kamtschatka
added a commit
to kamtschatka/hoarder-app
that referenced
this issue
Sep 23, 2024
…is configured hoarder-app#406 Added the DISABLE_LOCAL_SIGNUPS that can be used to force OAuth signups only
This was referenced Sep 23, 2024
MohamedBassem
added a commit
that referenced
this issue
Oct 6, 2024
* [Feature Request] Allow to disable default password log in after SSO is configured #406 Added the DISABLE_LOCAL_SIGNUPS that can be used to force OAuth signups only * rename local signups to password signups --------- Co-authored-by: MohamedBassem <me@mbassem.com>
kamtschatka
added a commit
to kamtschatka/hoarder-app
that referenced
this issue
Oct 6, 2024
…is configured hoarder-app#406 changed the flag to also disallow logging in via password The extensions will also no longer be allowed to log in via username/password then
kamtschatka
added a commit
to kamtschatka/hoarder-app
that referenced
this issue
Oct 8, 2024
…is configured hoarder-app#406 added the error message for OAuth
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reference: #92
Thank you for the wonderful project! And finally I can use SSO to secure my instance.
However after the SSO is set, can we add an env variable like DISABLE_DEFAULT_LOGIN or DISABLE_LOGIN_FORM to disable the default email and password log in form? Only through this way the SSO can properly protect the Hoarder itself.
Thank you so much for your effort again!
The text was updated successfully, but these errors were encountered: