You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When inviting an emergency contact, the invite fails with
Webinterface:
An error has occurred.
Grantee user does not exist: grantee@email.com.
Docker log:
vaultwarden | [2021-12-16 17:25:36.262][request][INFO] POST /api/emergency-access/invite
vaultwarden | [2021-12-16 17:25:36.264][vaultwarden::api::core::emergency_access][ERROR] Grantee user does not exist: grantee@email.com
vaultwarden | [2021-12-16 17:25:36.264][response][INFO] POST /api/emergency-access/invite (send_invite) => 400 Bad Request
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.
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:
An error has occurred.
Grantee user does not exist: grantee@email.com.
Docker log:
vaultwarden | [2021-12-16 17:25:36.262][request][INFO] POST /api/emergency-access/invite
vaultwarden | [2021-12-16 17:25:36.264][vaultwarden::api::core::emergency_access][ERROR] Grantee user does not exist: grantee@email.com
vaultwarden | [2021-12-16 17:25:36.264][response][INFO] POST /api/emergency-access/invite (send_invite) => 400 Bad Request
The text was updated successfully, but these errors were encountered:
tam1m
changed the title
Invite Emergency Contact fails when grantee email does is not already registered with an account
Invite Emergency Contact fails when grantee email is not already registered with an account
Dec 16, 2021
Confirmed. It should check if INVITATIONS_ALLOWED is 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_ALLOWED or just use the main one.
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:
The text was updated successfully, but these errors were encountered: