Feature name
Allow creation of Password protected exports from the Desktop App.
Feature function
Currently the Desktop App can only create Account restricted exports, but not Password protected exports. Implementing this feature in the Desktop app will allow users to do so without having to open up their web browser and login to their web vault.
3 Likes
When exporting a vault and selecting .json (Encrypted) as the file format, I get a choice between “Account Restricted” and “Password protected” when using the web version of BitWarden.
When using the Chrome Extension, I do not get an option for how to encrypt the vault when selecting .json (Encrypted) as the format.
Can the option to select “vault export encryption type” be made available in the Chrome Extension version?
grb
March 17, 2024, 2:39pm
3
I merged two related requests and changed the topic title to “Allow password protected exports from all apps and extensions” (was “Allow password protected exports from Desktop App”).
@outsider if you have any votes left to give, don’t forget to vote for your request by clicking the Vote button at the top of the thread.
Would actiualy be a great idea! and somewhere down the line choose a way asigned certificate / key, That you can choose to only make it work on your vaults & no hacker cannot use it even if they spoof your device and/or network/server to grab the *.json file and use it for their own benifits!
grb
March 19, 2024, 12:57am
5
@Darelw0010 No hacker can use a password-protected .json export “for their own benefits” unless you make a weak password or disclose the password.
djsmith85
(Daniel James Smith)
May 24, 2024, 1:43pm
6
Hey everyone,
just wanted to let you know that the following pull-requests are bringing password-encrypted exports to browser and desktop:
bitwarden:tools/pm-8254/create-shareable-export-component
← bitwarden:tools/pm-2516/add-password-protected-export-on-browser
opened 08:30AM - 21 May 24 UTC
## Type of change
```
- [ ] Bug fix
- [X] New feature development
- [ … ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other
```
## Objective
The introduction of a password-protected export was a great feature addition, but unfortunately until now was only available on web and the CLI.
This work adds the following features:
- Password protected exports are now available on browser
- Using the same visual component as the web vault for a more modern look (Follow-up PR to further modernize the UI with the Extension refresh following soon)
- With the recent introduction of flexible collections, user can now manage their assigned collection. As already possible on the web-vault members of an organization can now also export their managed collection from the browser extension
## Code changes
- **Create export-browser component using shared recipe -** https://github.com/bitwarden/clients/commit/d9b6dfe5026f1694334898eb172d2f1bd09fef3c
- Create new export component that uses the shared export.component from @bitwarden/vault-export-ui
- **Update imports within AppModule -** https://github.com/bitwarden/clients/commit/f73b53aee0d50cd95edc5673242de912b6029da3
- **Switch to route to the new component -** https://github.com/bitwarden/clients/commit/f740590815c3f8fe3bd9b6eb15663f6dd25547e7
- **Add missing entries to messages.json -** https://github.com/bitwarden/clients/commit/aa10835fd71469a6103ff717c001e331cc0d4963
- **Delete old export.component -** https://github.com/bitwarden/clients/commit/ce5a4af46a0129445b64cc29f3bf9688eab192b1
## Screenshots
### Before
![before_export](https://github.com/bitwarden/clients/assets/2670567/996c4e24-02c4-44f4-91af-f114404ac05e)
### After
![after_export1](https://github.com/bitwarden/clients/assets/2670567/c769c537-7173-4f75-9795-b8b9eaa2ed2b)
![after_export2](https://github.com/bitwarden/clients/assets/2670567/0274c6c5-8fcc-4575-8107-c20b75513649)
![after_org-export](https://github.com/bitwarden/clients/assets/2670567/cc66d21d-6331-477e-aa04-4e40b4d56fea)
## Before you submit
- Please add **unit tests** where it makes sense to do so (encouraged but not required)
- If this change requires a **documentation update** - notify the documentation team
- If this change has particular **deployment requirements** - notify the DevOps team
- Ensure that all UI additions follow [WCAG AA requirements](https://contributing.bitwarden.com/contributing/accessibility/)
bitwarden:tools/pm-8254/create-shareable-export-component
← bitwarden:tools/pm-2517/add-password-protected-export-on-desktop
opened 09:41AM - 21 May 24 UTC
## Type of change
```
- [ ] Bug fix
- [X] New feature development
- [ … ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other
```
## Objective
The introduction of a password-protected export was a great feature addition, but unfortunately until now was only available on web and the CLI.
This work adds the following features:
- Password-protected exports are now available on desktop
- Using the same visual component as the web vault for a more modern look
- With the recent introduction of flexible collections, org-members can now manage their assigned collections. As already possible on the web-vault, org-members can now also export their managed collection from the desktop app.
## Code changes
- **Create export-desktop component using shared recipe -** https://github.com/bitwarden/clients/commit/eb9f08facb4694c3c6fdca3b3231dc9a6c123c47
- Create new export component that uses the shared export.component from @bitwarden/vault-export-ui
- **Update imports within AppModule -** https://github.com/bitwarden/clients/commit/60f6d580119e2518dcb7e74482cf59f484d2e152
- Remove old ExportComponent
- Remove ExportScopeCalloutComponent as it's part of the BaseExportComponent
- **Open new component when clicking on Export Vault menu item -** https://github.com/bitwarden/clients/commit/e0392be3d8da96ca7e91efeb877de1d3388174e0
- **Add missing entries to messages.json -** https://github.com/bitwarden/clients/commit/ab75069e41a8aff2fa700153e3e2b7c3788e1d24
- **Delete old export.component -** https://github.com/bitwarden/clients/commit/12724eea702d7ee403686c4e595c21a3342999e5
## Screenshots
### Before
![before_export](https://github.com/bitwarden/clients/assets/2670567/99d89dae-e641-4a1d-a2eb-8df69d87d258)
### After
![after_export](https://github.com/bitwarden/clients/assets/2670567/1844a6f4-11ec-483d-bc45-89b25bc83ba8)
![after_org-export](https://github.com/bitwarden/clients/assets/2670567/76b8a2fd-9b0d-48af-8a3f-2746f3651d87)
## Before you submit
- Please add **unit tests** where it makes sense to do so (encouraged but not required)
- If this change requires a **documentation update** - notify the documentation team
- If this change has particular **deployment requirements** - notify the DevOps team
- Ensure that all UI additions follow [WCAG AA requirements](https://contributing.bitwarden.com/contributing/accessibility/)
Once these have passed QA and have been merged, they will be included in an upcoming release (possibly 2024.6
).
Kind regards,
Daniel
5 Likes
djsmith85
(Daniel James Smith)
August 12, 2024, 10:43am
7
Closing this request, as password protected export available on all clients with 2024.6.0
More information can be found on the release notes
1 Like
grb
August 12, 2024, 5:23pm
9
This doesn’t include mobile apps, though, right?
djsmith85
(Daniel James Smith)
August 12, 2024, 7:22pm
11
Yes, not on the old mobile apps, but is included in the new apps (currently in beta).
2 Likes