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 I try to decrypt the data.json file from a bitwarden cli test account I get the following error:
ERROR: MAC did not match. Protected Symmetric Key was not decrypted. (Password may be wrong)
This test account belongs to an organization, and if I purge the organization vault then I'm able to decrypt the data.json file just fine (to clarify: the account is still member of the organization, but it's vault is empty).
There has to be something about the org vault items decryption that's causing the error.
But I haven't been able to find out exactly what it is.
After some more testing I could reproduce the error with a single item in the organization vault that has an attachment. If I delete that attachment from the item, then I'm able to decrypt the data.json file again.
Thanks.
The text was updated successfully, but these errors were encountered:
Thanks for confirming. I'll create a new test account and try to reproduce this myself. I'll reach out to you if I need it but I think I should be okay.
When I try to decrypt the data.json file from a bitwarden cli test account I get the following error:
ERROR: MAC did not match. Protected Symmetric Key was not decrypted. (Password may be wrong)
This test account belongs to an organization, and if I purge the organization vault then I'm able to decrypt the data.json file just fine (to clarify: the account is still member of the organization, but it's vault is empty).
There has to be something about the org vault items decryption that's causing the error.
But I haven't been able to find out exactly what it is.
After some more testing I could reproduce the error with a single item in the organization vault that has an attachment. If I delete that attachment from the item, then I'm able to decrypt the data.json file again.
Thanks.
The text was updated successfully, but these errors were encountered: