mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
User is shown as "invited" even after creating an account and cannot be added to organization #1108
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 @tstoik on GitHub (Sep 4, 2021).
Subject of the issue
This has happened twice with users who previously had accounts but were removed when access needs changed. When they were removed, I removed them from the organization as well as deleted their accounts from the Vaultwarden Admin portal.
Eventually, they needed access again (this was not anticipated or I would not have deleted their accounts in the past). I reinvited them and they were able to create a new account, but now they permanently appear as "Invited" and I can't add them to the organization. The only solution we've found is to invite them with a different email address, which is not ideal. Is there a way to manually add them to the organization through another process?
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Steps to reproduce
Expected behaviour
I expected that deleted users would be erased from the instance entirely and could then be re-added as a brand new user as normal.
Actual behaviour
The user is stuck in a limbo state where they have an account on the server but the account cannot be connected to the organization and appears to still be invited even though they accepted the invitation
Troubleshooting data
@BlackDex commented on GitHub (Sep 4, 2021):
I can not reproduce this issue. It works fine for me.
This also isn't possible since when deleting the user via the admin interface everything regarding that user is removed.
It could be that that user used the wrong invite maybe.
I have tried it twice, with two different e-mails, and two different organizations, no way to reproduce it.
Please try again, and if it really doesn't work re-open this issue.