* refactor triggerChangedPasswordNotification logic
* improve triggerChangedPasswordNotification and test coverage to handle scenarios more comprehensively
* restore triggerChangedPasswordNotification logic and move new logic and testing to triggerCipherNotification
* add branching qualification logic for cipher notifications
* add and implement undetermined-cipher-scenario-logic feature flag
* add optional chaining to username comparison of existing login ciphers
* cleanup
* update tests
* prefer explicit length comparisons
Update Account Recovery flow to use new KM data types from `master-password.types.ts` / `MasterPasswordService`:
- `MasterPasswordAuthenticationData`
- `MasterPasswordUnlockData`
This allows us to move away from the deprecated `makeMasterKey()` method (which takes email as salt) as we seek to eventually separate the email from the salt.
Changes are behind feature flag: `pm-27086-update-authentication-apis-for-input-password`
- Updates `InputPasswordComponent` to emit raw data instead of generating cryptographic properties (`newMasterKey`, `newServerMasterKeyHash`, `newLocalMasterKeyHash`).
- This helps us in moving away from using the deprecated `makeMasterKey()` method in the component (which takes email as salt) as we seek to eventually separate the email from the salt.
- Updates the `JIT_PROVISIONED_MP_ORG_USER` case of the switch to handle the flow when the `PM27086_UpdateAuthenticationApisForInputPassword` flag is on.
Feature Flag: `PM27086_UpdateAuthenticationApisForInputPassword`
* Added encrypted default collection name to new feature flagged restore user methods/endpoint.
* corrected filter to use null check with imperative code
* add explicit checks and change remove listener to any in order to match add listener and chrome api
* address feedback
* when requestInitiator is falsy but active auto submit exists, cleanup should still occur
* add documentation to remove listener
* update message from vault handling to check against accounts or message sender
* update valid vault referrer logic to check all configured environments
* session key retrieval redesign for the local backed session storage
* typo
* incorrect substring
* get cache edge cases incorrectly handling to null values after removal
* test coverage
* internal `SessionKeyResolveService`
* dirt: migrate apps/web components to new control flow
* dirt: update control flow bitwarden licensed code
* consolidate @if statements, use @else where appropriate
* more cleanup
* consolidate conditionals
* remove unnecessary conditional
* Remove `ts-strict-ignore` from fido2 page
* Update typing issue
* Fix AssertCredentialResult type issue
* Remove non null assertions and add type guard
* Addresses topWindow non null assertion
* remove redundant check and remove ts strict from messenger
---------
Co-authored-by: Jonathan Prusik <jprusik@users.noreply.github.com>
Co-authored-by: Daniel Riera <driera@livefront.com>
- Renamed `activateAutofill` to `activateAutofillPolicy` in the policy order map and component.
- Updated corresponding translation keys in `messages.json` for consistency.
- Adjusted warning message in the `activate-autofill.component.html` to reflect the new naming convention.
* Refactor policy edit registration to centralize ownership and improve organization. Reordered policies for clarity and added new policies for enhanced functionality.
* Add PolicyOrderPipe for sorting policies and update policies component to utilize it
* Add organizationDataOwnership to POLICY_ORDER_MAP for policy sorting
* Fix PR comments
