[GH-ISSUE #516] How can I create user? #325

New issue

Closed

opened 2026-03-03 01:28:01 +03:00 by kerem · 5 comments

kerem commented

2026-03-03 01:28:01 +03:00

Owner

Originally created by @lukasmrtvy on GitHub (Jun 28, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/516

How can I create user if I am running bitwarden_rs with SIGNUPS_ALLOWED=false and
INVITATIONS_ALLOWED=false ?
Should I run it without SIGNUPS_ALLOWED=false, create user and then ..with admin panel disable signups?

Originally created by @lukasmrtvy on GitHub (Jun 28, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/516 How can I create user if I am running bitwarden_rs with `SIGNUPS_ALLOWED=false` and `INVITATIONS_ALLOWED=false` ? Should I run it without `SIGNUPS_ALLOWED=false`, create user and then ..with admin panel disable signups?

kerem closed this issue

2026-03-03 01:28:01 +03:00

kerem commented

2026-03-03 01:28:02 +03:00

Author

Owner

@dani-garcia commented on GitHub (Jun 28, 2019):

That's probably the way to go yeah. If you leave invitations open, you can also invite yourself from the admin panel, without keeping signups open to everyone.

@dani-garcia commented on GitHub (Jun 28, 2019): That's probably the way to go yeah. If you leave invitations open, you can also invite yourself from the admin panel, without keeping signups open to everyone.

kerem commented

2026-03-03 01:28:02 +03:00

Author

Owner

@lukasmrtvy commented on GitHub (Aug 6, 2019):

@dani-garcia something like:
BW_EMAIL and BW_PASSWORD/BW_GENERATE_PASSWORD env variables would be superusefull to create initial admin user.
Thanks

@lukasmrtvy commented on GitHub (Aug 6, 2019): @dani-garcia something like: `BW_EMAIL` and `BW_PASSWORD/BW_GENERATE_PASSWORD` env variables would be superusefull to create initial admin user. Thanks

kerem commented

2026-03-03 01:28:02 +03:00

Author

Owner

@dani-garcia commented on GitHub (Aug 6, 2019):

The problem with that is we would have to implement the password hashing and encryption key creation, which at the moment is entirely done on the client.

Another option to make sure the server is not exposed to the web before being configured is starting it with ROCKET_ADDRESS=localhost, which would only accept connections from the local machine.

@dani-garcia commented on GitHub (Aug 6, 2019): The problem with that is we would have to implement the password hashing and encryption key creation, which at the moment is entirely done on the client. Another option to make sure the server is not exposed to the web before being configured is starting it with ROCKET_ADDRESS=localhost, which would only accept connections from the local machine.

kerem commented

2026-03-03 01:28:02 +03:00

Author

Owner

@lukasmrtvy commented on GitHub (Aug 6, 2019):

And what about generating some unique URL, which will provide one click registration. ( It can be sent to mail, if SMTP vars will be defined, or may be visible in /admin or in log output )

@lukasmrtvy commented on GitHub (Aug 6, 2019): And what about generating some unique URL, which will provide one click registration. ( It can be sent to mail, if SMTP vars will be defined, or may be visible in /admin or in log output )

kerem commented

2026-03-03 01:28:02 +03:00

Author

Owner

@dani-garcia commented on GitHub (Aug 6, 2019):

It could be a good idea, but it probably requires modifying the clients to allow sending an extra field while registering.

@dani-garcia commented on GitHub (Aug 6, 2019): It could be a good idea, but it probably requires modifying the clients to allow sending an extra field while registering.