[GH-ISSUE #556] Disable all sign in requirements? #360

Closed
opened 2026-03-02 11:49:11 +03:00 by kerem · 9 comments
Owner

Originally created by @wbste on GitHub (Oct 16, 2024).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/556

Hey, awesome work so far! If one were to run this locally with no public Internet exposure, is it possible to just disable any sign in requirements? Just want to jump straight into the app. I saw I can disable the form and odic login...if I already created one account does that mean I get locked out? Or auto log in?

https://docs.hoarder.app/configuration

Originally created by @wbste on GitHub (Oct 16, 2024). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/556 Hey, awesome work so far! If one were to run this locally with no public Internet exposure, is it possible to just disable any sign in requirements? Just want to jump straight into the app. I saw I can disable the form and odic login...if I already created one account does that mean I get locked out? Or auto log in? https://docs.hoarder.app/configuration
kerem 2026-03-02 11:49:11 +03:00
Author
Owner

@Inventhrice commented on GitHub (Oct 17, 2024):

So far, there is no way to disable authentication in the application. I have the DISABLE_SIGNUPS flag enabled, so I can confirm it shows the landing page where you can login, but you would not have any capability of signing up new users.

Tossing my two cents: Disabiling auth is a really cool idea (said nobody, i know) because there is merit to the idea of just hitting run and going. However, I also don't know how that would be implemented, as to support multiple users you would need some form of auth.

<!-- gh-comment-id:2419837450 --> @Inventhrice commented on GitHub (Oct 17, 2024): So far, there is no way to disable authentication in the application. I have the DISABLE_SIGNUPS flag enabled, so I can confirm it shows the landing page where you can login, but you would not have any capability of signing up new users. Tossing my two cents: Disabiling auth is a really cool idea (said nobody, i know) because there is merit to the idea of just hitting run and going. However, I also don't know how that would be implemented, as to support multiple users you would need some form of auth.
Author
Owner

@wbste commented on GitHub (Oct 17, 2024):

For this use case, the user base is a single user. There's no need to support additional users.

<!-- gh-comment-id:2420144700 --> @wbste commented on GitHub (Oct 17, 2024): For this use case, the user base is a single user. There's no need to support additional users.
Author
Owner

@MohamedBassem commented on GitHub (Oct 17, 2024):

I think the best we can do is if you have OIDC enabled, and password auth disabled, we can add a new flag AUTO_OAUTH_LOGIN which if enabled, we can start the oauth workflow automatically when you land on the signup page. Would that work for you?

<!-- gh-comment-id:2420658514 --> @MohamedBassem commented on GitHub (Oct 17, 2024): I think the best we can do is if you have OIDC enabled, and password auth disabled, we can add a new flag `AUTO_OAUTH_LOGIN` which if enabled, we can start the oauth workflow automatically when you land on the signup page. Would that work for you?
Author
Owner

@wbste commented on GitHub (Oct 18, 2024):

Nah, sorry for not being clear. I would like to NEVER sign in, ever. No username and password, no SSO, no nothing. Anyone with access to the app would be "the same user" with full access. The obvious ramifications are if anyone else were to access the app they would not need to authenticate and would see all my stuff.

Maybe on the docker compose set a default username and password, and if DISABLE_SIGNUPS
and DISABLE_PASSWORD_AUTH are both true and no oauth is config'd then it auto logs in as that user?

Not a huge deal if it's a pain, just a nice to have. Thanks again for an awesome app!

<!-- gh-comment-id:2421119190 --> @wbste commented on GitHub (Oct 18, 2024): Nah, sorry for not being clear. I would like to NEVER sign in, ever. No username and password, no SSO, no nothing. Anyone with access to the app would be "the same user" with full access. The obvious ramifications are if anyone else were to access the app they would not need to authenticate and would see all my stuff. Maybe on the docker compose set a default username and password, and if `DISABLE_SIGNUPS` and `DISABLE_PASSWORD_AUTH` are both true and no oauth is config'd then it auto logs in as that user? Not a huge deal if it's a pain, just a nice to have. Thanks again for an awesome app!
Author
Owner

@tjhart85 commented on GitHub (Oct 18, 2024):

FWIW, I would absolutely love an 'AUTO_OAUTH_LOGIN' flag as for my household that would be fantastic and our phones and PCs are basically always logged in (and if they're not, this will prevent them from needing to be for the next program we use, so no biggie).

I understand OP though, for the apps I have that are single user, local network only, I do find it very annoying when they mandate a login policy (especially when they don't allow OIDC!)

<!-- gh-comment-id:2422588864 --> @tjhart85 commented on GitHub (Oct 18, 2024): FWIW, I would absolutely love an 'AUTO_OAUTH_LOGIN' flag as for my household that would be fantastic and our phones and PCs are basically always logged in (and if they're not, this will prevent them from needing to be for the next program we use, so no biggie). I understand OP though, for the apps I have that are single user, local network only, I do find it very annoying when they mandate a login policy (especially when they don't allow OIDC!)
Author
Owner

@nicktheone commented on GitHub (Oct 21, 2024):

Completely agree. I came here looking for this exact request, in case it had already been made. I understand the need for a robust user management system but in case of an instance walled behind a VPN with no other access to the Internet there isn't really any need for authentication nor authorization. I have several other self hosted apps that can optionally disable log in prompts and if Hoarder followed suit it'd amazing.

<!-- gh-comment-id:2427248203 --> @nicktheone commented on GitHub (Oct 21, 2024): Completely agree. I came here looking for this exact request, in case it had already been made. I understand the need for a robust user management system but in case of an instance walled behind a VPN with no other access to the Internet there isn't really any need for authentication nor authorization. I have several other self hosted apps that can optionally disable log in prompts and if Hoarder followed suit it'd amazing.
Author
Owner

@Inventhrice commented on GitHub (Oct 22, 2024):

To be clear on my end as well, would LOVE for this to be a feature!! It does get a bit tiresome to keep logging in.

<!-- gh-comment-id:2428196166 --> @Inventhrice commented on GitHub (Oct 22, 2024): To be clear on my end as well, would LOVE for this to be a feature!! It does get a bit tiresome to keep logging in.
Author
Owner

@randrums commented on GitHub (Apr 10, 2025):

I have karakeep working. I signed up as the first user, but now I can't figure out how to disable signups.

I stopped all containers, and re-deployed it with the variable DISABLE_SIGNUPS set to TRUE, but the Sign Up is still available. Could someone help me with getting it disabled?

<!-- gh-comment-id:2794879248 --> @randrums commented on GitHub (Apr 10, 2025): I have karakeep working. I signed up as the first user, but now I can't figure out how to disable signups. I stopped all containers, and re-deployed it with the variable **DISABLE_SIGNUPS** set to TRUE, but the Sign Up is still available. Could someone help me with getting it disabled?
Author
Owner

@emanuele-bordon commented on GitHub (May 17, 2025):

I have karakeep working. I signed up as the first user, but now I can't figure out how to disable signups.

I stopped all containers, and re-deployed it with the variable DISABLE_SIGNUPS set to TRUE, but the Sign Up is still available. Could someone help me with getting it disabled?

Same for me..

<!-- gh-comment-id:2888480708 --> @emanuele-bordon commented on GitHub (May 17, 2025): > I have karakeep working. I signed up as the first user, but now I can't figure out how to disable signups. > > I stopped all containers, and re-deployed it with the variable **DISABLE_SIGNUPS** set to TRUE, but the Sign Up is still available. Could someone help me with getting it disabled? Same for me..
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/karakeep#360
No description provided.