* Changes for the reseller alert
* Resolve the null error
* Refactor the reseller service
* Fix the a failing test due to null date
* Fix the No overload matches error
* Resolve the null error
* Resolve the null error
* Resolve the null error
* Change the date format
* Remove unwanted comment
* Refactor changes
* Add the feature flag
The first pass of the integration logic mixed names between
"integration" and "extension". For example, the remote service
has an "IntegrationId" whereas the part of the password manager
it extended has an "ExtensionPointId".
The new types have a more consistent approach. The remote
service now distinguishes the integrated product from the
vendor providing it, and the logic within the password manager
is now all the "extension". The specific location being extended
is now called the "site" or "extension site".
The main reason "extension" was chosen over "integration" is simply
so that the new and old types remain distinct in the folder hierarchy.
This PR deletes the legacy lock components from the Angular clients and also removes feature flag control from the routing. The lock component will now be based entirely on the new, recently refreshed LockComponent in libs/auth/angular.
* update cipher-view to account for strict type checking
* update view-identity-sections to account for strict type checking
* update read-only-cipher-card to account for strict type checking
* remove unused card import
* remove unused card import
* update additional-options to account for strict type checking
* show color password for visible passwords in vault view
- The password input will be visually hidden
- Adds tests for the login credentials component
* formatting
* feat: re-implement getEnvironment as an observable
* feat: deprecate `getEnvironment`
* fix: use correct environment function in SdkService
* fix: test
* add account created date to the account information
* set permanent dismissal flag when the user selects that they can access their email
* update the logic of device verification notice
* add service to cache the profile creation date to avoid calling the API multiple times
* update step one logic for new device verification + add tests
* update step two logic for new device verification + add tests
- remove remind me later link for permanent logic
* migrate 2FA check to use the profile property rather than hitting the API directly.
The API for 2FA providers is only available on web so it didn't work for browser & native.
* remove unneeded account related changes
- profile creation is used from other sources
* remove obsolete test
* store the profile id within the vault service
* remove unused map
* store the associated profile id so account for profile switching in the extension
* add comment for temporary service and ticket number to remove
* formatting
* move up logic for feature flags
* force viewOnly to be true for emergency access
* add input to hide password history, applicable when the view is used from emergency view
* add extension refresh version of the emergency view dialog
* allow emergency access to view password history
- `ViewPasswordHistoryService` accepts a cipher id or CipherView. When a CipherView is included, the history component no longer has to fetch the cipher.
* remove unused comments
* Add fixme comment for removing non-extension refresh code
* refactor password history component to accept a full cipher view
- Remove the option to pass in only an id
* starting
* setup first page for new device verification notice
* update designs for first page. rename components and files
* added second page for new device verification notice
* update notice page one with bit radio buttons. routing logic. user email
* updated routing for new device verification notice to show before vault based on flags, and can navigate back to vault after submission
* fix translations. added remind me later link and nav to page 2
* sync the design for mobile and web
* update routes in desktop
* updated styles for desktop
* moved new device verification notice guard
* update types for new device notice page one
* add null check to page one
* types
* types for page one, page two, service, and guard
* types
* update component and guard for null check
* add navigation to two step login btn and account email btn
* remove empty file
* update fill of icons to support light & dark modes
* add question mark to email access verification copy
* remove unused map
* use links for navigation elements
- an empty href is needed so the links are keyboard accessible
* remove clip path from exclamation svg
- No noticeable difference in the end result
* inline email message into markup
---------
Co-authored-by: Nick Krantz <nick@livefront.com>
This PR adds a logout option to the TDE approval screen. A TDE user on this page cannot use the "Back" button or click the Bitwarden logo to navigate back to `/` because the user is currently authenticated, which means that navigating to the `/` route would activate the `redirectGuard` and simply route the user back to `/login-initiated`. So we must log the user out first before routing.
Feature Flags: `UnauthenticatedExtensionUIRefresh` ON
* Add tests to verify importing German and Dutch headers work
* Add method to translate the headers from (German/Dutch into English) while the CSV data is being parsed
* Report "importFormatError" when header translation did not work, instead of a generic undefined error (startsWith)
* Move passwordxp-csv-importer into a dedicated folder
* Introduce files with the language header translations
---------
Co-authored-by: Daniel James Smith <djsmith85@users.noreply.github.com>
* add user asymmetric key api service
* Add user asymmetric key regen service
* add feature flag
* Add LoginSuccessHandlerService
* add loginSuccessHandlerService to BaseLoginViaWebAuthnComponent
* Only run loginSuccessHandlerService if webAuthn is used for vault decryption.
* Updates for TS strict
* bump SDK version
* swap to combineLatest
* Update abstractions
Intercepts browser back button press on the login screen to properly
transition back to email entry portion instead of unexpected navigation.
Resolves PM-15987
* use organization properties for access permissions
* clean up refactor
* simplify logic
* refactor canAccessIntegrationEditor to have all the permission checks
This PR fixes a bug in the LockComponent refresh that affected the setup/save and use passkey flows. The user was wrongly directly to the /vault after unlock instead of to /fido2 (the passkey screen).
Feature Flag: ExtensionRefresh ON
