Because:
* Redirect back to /subscriptions after signin was not working
This commit:
* Pass the redirectTo as search param
* Validate the redirectTo and if valid navigate there after signin
Closes #FXA-9826
Because:
* Users would be taken to the 2FA page from signin_token_code when they hadn't yet verified 2FA
* There's an edgecase at least in Sync signin causing an invalid token code on this page
This commit:
* Checks for totp verified instead of totp exists
* Uses the sessionToken passed into the component instead of useSession, which was causing console errors
fixes FXA-9836
Because:
- The events were rejected because the 'ts' field was missing
- In auth server this added in by the logger, so it wasn't initially detected
This Commit:
- Adds the ts field to all profileDataChange events emitted by admin-server
- Updates the DTO support additional optional fields
Because:
* Users are signed into the browser, but Sync is "off"
This commit:
* Adds { services: sync: {} } to the fxaLogin web channel message to start Sync
fixes FXA-9791
Because:
- We were always using v1 ks
- This won't work for an account that has been upgraded to v2 ks
This Commit:
- Gets client salt and current ks version for account
- Fixes bug in gql. The version field should have been called currentVersion.
Because:
- The email was still going out, even though the previous change attempted to stop this
- The logic to determine whether or not we were in upgrade state was always false
This Commit:
- Fixes the logic to determine whether or not we were in upgrade state
Because:
- the React + gql-api sign in unblock does not handle the "incorrect
email" error when the user sign in with a new primary email
This commit:
- retries the unblock sign in with the original sign up email
Because:
- Admin server wasn't starting up cleanly
- NotifierService dependencies weren't being provided
This Commit:
- Adds MozLoggerService to providers
- Adds LegacyStatsDProvider to providers
- Removes SentryModule, which is deprecated in favor of direct initialization
Because:
- We found a bug that occurred during sign in after swapping secondary and primary emails.
This Commit:
- Makes sure to send up the 'originalEmail'
Because:
- AccountCustomerManager.createAccountCustomer included updateAt as a
parameter even though it wasn't used.
This commit:
- Remove updateAt from createAccountCustomer and update related files.
Closes #
Because:
* We have a new password reset flow that uses confirmation codes instead of link
This commit:
* Remove backbone resetPassword playwright page object model (POM), no longer in use
* Move all reset password tests out of react-conversion folder, and into new resetPassword folder with subfolders for resetPasswordWithLink and resetPasswordWithCode
* Mark the functional tests for reset password with link for deletion with ticket number
* Add new tests updated for reset password with code flow in resetPasswordWithCode folder
* Fix bug with password strength bubble not displayed due to discontinued onFocus metric
Closes #FXA-9612
Because:
* Form submission should be disabled when there was an error on submit
* Re-enable submit after the code is changed
* We want to prevent the user from accidentally hitting the verification limit by submitting the same wrong code too many times
* We do not want the submit button to be disabled if the error is caused by a resend code error
This commit:
* Update the conditions where the submit button in FormVerify code component is disabled
* Remove the aria-label on submit button that was reading the code
* Separate the resend code error state from code verification error state
* Clear all banners before code verification and code resend to make way for new messages
Closes #FXA-9724
Because:
- During development it could be useful to start only parts of the stack
needed for development on specific domains.
This commit:
- Provides additional stack startup options to only start specific parts
of the stack, by using nx projects and tags.
Closes #FXA-9771