-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when trying to export unencrypted organization vault via web interface #2764
Comments
Duplicate of #2760 |
Is this the same? #2760 only speaks to cli. I am unable to create backups via GUI. This should be a bug, not an enhancement, no? |
Yes it is the same. It's the exact same endpoint (and I changed the title). |
What is the last known-good version if I wanted to roll back? This was my first effort with bitwarden/vaultwarden |
I would suggest to use the |
Since v2022.9.x it seems they changed the export endpoint and way of working. This PR fixes this by adding the export endpoint. Also, it looks like the clients can't handle uppercase first JSON key's. Because of this there now is a function which converts all the key's to lowercase first. I have an issue reported at Bitwarden if this is expected behavior: bitwarden/clients#3606 Fixes dani-garcia#2760 Fixes dani-garcia#2764
Since v2022.9.x it seems they changed the export endpoint and way of working. This PR fixes this by adding the export endpoint. Also, it looks like the clients can't handle uppercase first JSON key's. Because of this there now is a function which converts all the key's to lowercase first. I have an issue reported at Bitwarden if this is expected behavior: bitwarden/clients#3606 Fixes #2760 Fixes #2764
Subject of the issue
Plaintext export of personal vault data works as expected. It is also possible to create an encrypted_json export of organization data. Plaintext exports of Organization vaults fail for both .csv and .json.
Encrypted exports are not useful for disaster recovery, where it is entirely possible the encryption key may be lost, preventing re-import of an encrypted .json file.
Unencrypted exports are essential for proper backups
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Steps to reproduce
After logging in as the Organization owner, then Organizations -> MyOrganization -> Tools -> Export Vault
Expected behaviour
Unencrypted .json file with organization vault data
Actual behaviour
Selecting File Format "Encrypted .json" and entering Master Password returns encrypted .json file.
Selecting ".json" or ".csv" produces "An unexpected error has occured" in the GUI
Troubleshooting data
With extended logging enabled and LOG_LEVEL=info, the following appears in the log
Setting LOG_LEVEL=debug and trying again produces identical output in the log.
Trying to do export with bw cli results in same issues as #2760
The text was updated successfully, but these errors were encountered: