mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #5127] Organization Member Management / User invitation broken #2078
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
pull-request
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#2078
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 @spacepope on GitHub (Oct 24, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5127
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Vaultwarden Build Version
v1.32.2
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx (Synology reverse proxy)
Host/Server Operating System
NAS/SAN
Operating System Version
DSM 7.2.1-69057 Update 5
Clients
Web Vault
Client Version
v2024.6.2c
Steps To Reproduce
What i did (not sure if this is reproducible by everyone):
Expected Result
Actual Result
As already described in the steps above:
Logs
No response
Screenshots or Videos
No response
Additional Context
After enabling Vaultwardens admin page to generate the log string for this issue, i noticed in the user tab, that the user, which i deleted within WebVault's organization member page, still exists within the database.
Kind of makes sense to not loose data, but within WebVault there is no way to see that the user still exists, or is there?
@BlackDex commented on GitHub (Oct 24, 2024):
Removing a user from an org doesn't delete the account, as you figured out your self too. A user might still have personal items or is part of more then on org. Therefore, such users need to login to accept the invite, and can't create a new account.
The user status will be updated if a user fully accepted the invite, and then the owner/admin needs to refresh/reload the page to see the changed status. Mostly clicking away from the members overview and back again is enough.
This is all works as intended.