* Add support for bulk deleeting org users
* Rename to UserBulkDeleteRequest
* Combine UserBulkReinviteRequest and DeleteRequest to OrganizationUserBulkRequest
* Increase error checking on imported Login items
* Check encKey when importing encrypted JSON
* Fix style, use GUID as random string for test
* Revert "Increase error checking on imported Login items"
This reverts commit 17294527863cc53b84ed218f94ffbc21f4e96260.
* fix linting
* Fix tests
* Set default cipher.reprompt value for imports
* Set default cipher.reprompt value for new ciphers
* Add support for importing bitwarden exports
* Add default cipher.reprompt for JSON imports
Co-authored-by: Hinton <oscar@oscarhinton.com>
* Add support for parsing .csv files from Nordpass
* Remove whitespace before extracting CardExpiration
* Add curlybraces to one-liner if's as requested
* NordPassImporter: Process more complex names
* Allow external awaits of indexing
We were getting stuck in an infinite load loop where we were basing
logic on a dirty state of search service. This await enables us to
wait until an index is complete, then update it rather than being
kicked out of indexing early because it is in progress.
* Stop infinite loop by specifying ciphers to index
* Specify Organization indexed on search service
a null indexedEntityId specifies it is the users entire vault.
otherwise, organizations specify their id to signify the index is a subset.
user's vault will re-index if the indexed entity does not match the
users id or null. at the moment, user's vault does not set userId
because indexing occurs in the setter for decryptedCipherCache,
which cannot be asynchronous
* Linter fix
This is needed for CLI to download Send files from non-configured
Bitwarden Servers. Web does not have this issue because it can assume
api from its own url.
* Upload correct data array
* Require BufferArray Encryption for upload to server
The CipherArrayBuffer tiny type is only created by CryptoService
and required by all upload methods
* Add test for attachment upload encryption
* Skip FirefoxAccounts during Firefox CSV Import
Firefox exports 'chrome://FirefoxAccounts' if Firefox Accouts are used
in browser. It's quite hacky - password field in CSV is actually a JSON
encoded data, not a password.
Because it's not a useful record, it should be skipped during import.
* Fix indentation
* Move test Firefox test data to files, fix linter errors
* Add collections to ciphers in export model.
This enables immediately setting collections from the CLI on create.
The other location this code is used is on import of Bitwarden json data.
However, collectionId is explicitly nulled out here to be resolved
later at the server level.
* Linter fix
