mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-02 22:57:18 -05:00
Incoherent user "enabled" status across admin interfaces #2426
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2426
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @dawagner on GitHub (Oct 30, 2025).
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
1.34.3
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
haproxy
Host/Server Operating System
Linux
Operating System Version
No response
Clients
Web Vault
Client Version
2025.7.0
Steps To Reproduce
I found this out while struggling to invite a user. Said user was formerly invited/enabled and subsequently revoked ; I don't remember exactly what I did in between but I ended up removing the user entirely and create it again via an LDAP synchronization.
The user was unable to sign in. They got a "user has been disabled" error message even though they appeared as enabled in the admin console.
I was going to report this issue but the ticket creation steps require going to
/admin/diagnosticsand this led me to discover this second admin interface. In that interface's, the user did appear as disabled. I was able to re-enable them there and solve my issue but I thought you might like to hear about this discrepancy.Expected Result
N/A
Actual Result
N/A
Logs
Screenshots or Videos
No response
Additional Context
No response
@stefan0xC commented on GitHub (Nov 24, 2025):
How did you remove the user? As far as I know a user can only be disabled via the
/admininterface. Removing a user from an Organization via the Admin Console should not disable the user account and removing them via the/admininterface should delete everything associated with that record.@dawagner commented on GitHub (Nov 24, 2025):
In two steps, calling two different APIs:
api/organizations/{orga_id}/users/{user_id}/revokeadmin/users/{user_id_in_admin_api}/disableI'm not sure I can say why it's done like this: I inherited this procedure.
Best regards
@stefan0xC commented on GitHub (Nov 24, 2025):
Well, that's at least an explanation for why the user account was disabled.
Because there's a different endpoint (
/admin/users/<user_id>/delete) to delete a user:github.com/dani-garcia/vaultwarden@7c7f4f5d4f/src/api/admin.rs (L414-L420)@BlackDex commented on GitHub (Nov 24, 2025):
I also think we can't really adjust this, as Bitwarden doesn't provide a feature to disable a user in general, in the sense to prevent the login.
I also think that removing a user from all ORG's when disabled might also cause confusion of course.
And, there is no way for us to somehow add a notice that the user is disabled in a normal way.
@dawagner commented on GitHub (Nov 25, 2025):
Thanks for your insights!
Our procedure allows for the possibility that the disabled/revoked/whatever user might be allowed back within a few months (if not, we eventually delete them completely from vaultwarden). If I understand correctly, we should just call the
admin/users/{user_id_in_admin_api}/disableendpoint and not the other one?