mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #77] Getting '[error: cannot decrypt]' when using organisations #37
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#37
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 @dabeeeenster on GitHub (Jul 12, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/77
[error: cannot decrypt]@mprasil commented on GitHub (Jul 12, 2018):
Sounds like you didn't confirm the second account from the Organization owner (the first account)
There are two steps, first you invite, then you confirm the invited user. (in original server there's mid step of user confirming they want to join Organization, but that one is skipped with bitwarden_rs as we don't have email functionality to send the invitation)
@mprasil commented on GitHub (Jul 12, 2018):
I tried to reproduce this, but I can't. The only time I can see the "cannot decrypt" message is when the user is invited, but not yet confirmed. In the image bellow you can see Test2 user being in such state. (the list shows they are "accepted") You just need to confirm the user and they should see the cypher after they sync.
@dabeeeenster commented on GitHub (Jul 13, 2018):
Thanks for the replies - this was as described - I still needed to confirm the second user. I guess SMTP config would be helpful here.
@mprasil commented on GitHub (Jul 13, 2018):
As per discussion with Dani, I've created #80 to fix this. We shouldn't really be showing you the ciphers in the first place.