* [Reset Password] BUG - Update local policies for enforcement
* Updated with blocking sync
* add the stuff I forgot to tell vsalucci about
* removed the lies I fed vsalucci
* remove unnecessary import
Co-authored-by: Matt Portune <mportune@bitwarden.com>
* Dynamic theme switching and visual tweaks
* update action runner to use macos-11 for iOS 15 support
* additional tweaks
* refinements
* refinements
* formatting and tweaks
* [Reset Password v1] Update Temp Password
* fixed order of operations for reset temp password flow
* Refactored bool with auth result
* Finished removal of temp password flow from set password
* iOS extension support plus extension bugfixes
Co-authored-by: addison <addisonbeck1@gmail.com>
Co-authored-by: Matt Portune <mportune@bitwarden.com>
* Add captcha to login models and methods
* Add captcha web auth to login
* Extract captcha to abstract base class
* Add Captcha to register
* Null out captcha token after each successful challenge
* Cancel > close
* Move continue to a button
* Resolve pr comments
* Move use another two step method button
* Resolve code suggestions
* Resolve for iPhone
* Apply suggestions from code review
Co-authored-by: Thomas Rittson <31796059+eliykat@users.noreply.github.com>
Co-authored-by: Thomas Rittson <31796059+eliykat@users.noreply.github.com>
* Add HashPurpose parameter to HashPasswordAsync
* Use 2 iterations for local password hashing
* Force logout if user has old keyHash stored
* Revert "Force logout if user has old keyHash stored"
This reverts commit 497d4928fa.
* Add backwards compatability with existing keyHash
* Make card number hidden
* Add support for password reprompt
* Rename PasswordPrompt to Reprompt
* Protect autofill
* Use Enums.CipherRepromptType
* Fix iOS not building
* Protect iOS autofill
* Update to match jslib
* Fix failing build
* Explain how to verify email for file Sends
* Revert "Explain how to verify email for file Sends"
This reverts commit b72314bc93.
* Explain how to verify email for file Sends
both iOS and Android are having trouble with the current method
of loading the entire file to memory, encrypting it, and sending
to azure in one go.
We will need to come up with a chunking scheme to support
larger files in the future
