mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Admin Panel #108
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @joe217 on GitHub (Oct 6, 2018).
Hi,
Any thoughts on getting the admin panel working?
Usually accessible at my.bitwardendomain.com/admin?
@fbartels commented on GitHub (Oct 6, 2018):
I think that has been previously discussed at https://github.com/dani-garcia/bitwarden_rs/issues/202
@mprasil commented on GitHub (Oct 6, 2018):
Yeah, there actually isn't much we could use from upstream in this case and generally is too much work for little benefit. If there's something specific you'd like to do in it, it's usually easy enough to do directly with sqlite client on the db.
Feel free to ask if you want to do something specific.
I'm closing this as duplicate of #202
@joe217 commented on GitHub (Oct 9, 2018):
Thank you for the prompt response...and my apologies for missing the recent similar post.
Two quick follow-up quesitons:
Thanks!
@fbartels commented on GitHub (Oct 9, 2018):
@joe217 the linked ticket has this example:
sqlite3 data/db.sqlite3 "select * from users;"@joe217 commented on GitHub (Oct 9, 2018):
Ok. Thank you. Figured that out now. That produces mostly gibberish,
though. The username emails are in plaintext. How would I go about deleted
them?
Also, would working on the bw-data file be equivalent to working in the
actual container?
Thanks.
On Mon, Oct 8, 2018 at 10:09 PM Felix Bartels notifications@github.com
wrote:
@fbartels commented on GitHub (Oct 9, 2018):
You can find a comprehensive tutorial on sqlite at https://www.tutorialspoint.com/sqlite/
The reason for the "gibberish" is that it outputs all the data in the table. Looking at it a bit closer you the following probably give a more meaningful output
sqlite3 data/db.sqlite3 "select uuid,email from users;"In the end you probably want something like:
sqlite3 data/db.sqlite3 "delete from user where email='bla@company';"(untested)@mprasil commented on GitHub (Oct 9, 2018):
Careful with the deletes though, the user has a lot of attached objects in the DB. The best thing to do would be to change his password to some string like "deactivated" or something like that. This will never match the hashed passphrase and will effectively disable the account.
@joe217 commented on GitHub (Oct 11, 2018):
https://github.com/dani-garcia/bitwarden_rs/issues/212#issuecomment-428093496
`sqlite3 data/db.sqlite3 "select uuid,email from users;"
So the above does produce a very organized list of users. But best not to delete? If I want to change the password, how to do that? Can that same email ever be used again - after changing the password? I would suspect no?
@dani-garcia commented on GitHub (Oct 11, 2018):
This should disable the user and free the email to be used again:
Note: the 'disabled1' value could be anything, I just used that to make sure it wouldn't clash with a real email address.
The email is used when calculating the password hash at login by the client, which means it couldn't be possible to login again after that command. The command also deletes the users encryption keys for good measure.
The problem with deleting users is that there isn't currently any method to delete all the data assotiated with them unless you can login as the user yourself (In which case you can use the web vault option).