* 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
* 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
* Add direct attachment download and upload API endpoints
* Use direct download method
Enable download of emergency access attachments through EmergencyAccessId
* Match new Server model items
* New Server model for creating attachments.
Provides a url to upload data to, the type of upload, and the Cipher Response expected by the previous call
* Use direct upload url and scheme
* Report Failed single shot azure uploads
* Add cipher attachment upload to file upload service
* Deprecate legacy api methods
* Handle old servers missing new upload api methods
* Improve Send error handling
* Fallback attachment downloads on new endpoint not found
Limit upload size to the new 500MB
* Improve error handling
* lint fixes
This is in conjunction with API changes that validates the last known
revision date provided here with the actual last revision date on the
server to block potential data loss due to client desyncs.
Co-authored-by: Matt Gibson <mdgibson@Matts-MBP.lan>
Instead of updating it every time you call getNext(), it will be updated in a separate call, to avoid updating the index when the cipher did not auto-fill correctly (e.g wrong frame)
Fixes#1392
* Add new method for cycling through every login
To be used from browser extension when autofilling.
Related PR: https://github.com/bitwarden/browser/pull/956
* Cache sorted ciphers by URL and invalidate them after a period of 5 seconds
* Move file to models
* Update typescript to 3.6.5 along with tslint to latest.
* Upgrade @types/node to 12.12.54 to get rid of compile errors.
* Update tslint.
* Use @types/node 10.17.28 instead
