mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-11 09:13:02 +03:00
Invite Emergency Contact fails when grantee email is not already registered with an account #1244
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 @tam1m on GitHub.
Subject of the issue
When inviting an emergency contact, the invite fails with
Webinterface:
Docker log:
This is not how it is supposed to work as the webinterface states that
If they do not have a Bitwarden account already, they will be prompted to create a new account.Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Steps to reproduce
Add emergency contact via webinterface, where the grantees email, is not already registered with an account
Expected behaviour
Vaultwarden sends an email invitation to the grantees email address. Same behaviour as invite to organization
Actual behaviour
Vaultwarden gives the following error message
Webinterface:
Docker log:
@BlackDex commented on GitHub:
Confirmed. It should check if
INVITATIONS_ALLOWEDis enabled. Though i could even argue that we may need a different config item for this. Since this would allow anybody who has an account to create new accounts/invites for everybody. While this feature first was only able to be used by Organization Managers, Admins and Owners. Though, basic users were already able to create organizations them selfs, and then invite other uses if this was set to true.What do you think @dani-garcia and @jjlin ? Should this be a separate config item like
EMERGENCY_INVITATIONS_ALLOWEDor just use the main one.