Because:
* We are prepping for SMS work and want to make some small UX improvements
This commit:
* Creates HeadingPrimary for our grey h1 text at the top of our flows that we are moving towards
* Updates copy and styling for 2FA signin and reset password
closes FXA-10210
Because:
* We are updating the design of all banners
* We are also updating the alertBar styling
This commit:
* Add new Banner component and delete the previous version (now unused)
* Add new icon components needed for banner and make small tweaks to existing icons, ensure all minified with .min extension
* Replace Image used in SigninTokenCode, ConfirmSignupCode, SigninUnblock (use EmailCodeImage instead of MailImage which referenced an emailed link)
* Update alertBar component, add stories, update tests
* Update components and pages that use the Banner component
* Update tests and stories
Issue #FXA-9714
Because:
- when an account has an unverified 2fa and the user opt to not use the
recovery key, we should not prompt for the TOTP during password reset
This commit:
- ensures that 2fa is enabled, exists and verified, for the account
Because:
- we want to automatically generate a new recovery key for the account
when the previous one was used for a password reset so that the user
does not need to do it manually
This commit:
- generates a new recovery key and present it to the user if a recovery
key was used during a password reset
Because:
* We want to redirect to relying party after successful password reset
* We want to handle cases where the RP requires totp (after password reset)
* Handle totp verification after password reset
This commit:
* Update styling of the ResetPasswordConfirmed component
* Add container component to ResetPasswordConfirmed to handle navigation to relying party and/or unverified session state after password reset
* Handle TOTP required error on retrieving oauth redirect
* Ensure signin after password reset continues to work for web and sync integrations, with or without verified session
* Update functional tests
Closes #FXA-9561
Because:
* We want to clarify some of the reset password warning wording
* We want to provide a link back to account_recovery_confirm_key on the complete_reset_password page when the user ininitially chooses not to use their key
* We want to show a warning message if we can't determine if the user has a recovery key (instead of an error)
* Also show the warning to users signing in to sync, even if they don't have actively synced devices (signing out from sync removes the device from estimated device count, but does not mean the user does not have synced data)
This commit:
* Update warning message and associated l10n, stories, tests
* Update CompleteResetPassword page to add link conditionally
* Some styling tweaks
Closes #FXA-10483
Because:
- the user could have a verified session after successfully resetting
their password for an account
This commit:
- logs the account in and take the user to /settings if the session is
verified and the user did not use a recovery key during the reset
Because:
- We have an unhandled exception being reported when a window changes focus on the /settings page and an account cannot be located in the apollo client cache
This Commit:
- Improves robustness of the handleWindowFocus routine
- Accounts for the possibility that the apollo cache could empty
- Accounts for the possibility that local storage could have been cleared
- Allows apolloClient to run in ‘dev’ mode for local development, which lets us introspect the cache using apollo dev tools and access the current apollo client in functional tests.
Because:
* Page was redesigned, needs new strings and left-alignment
This commit:
* Update copy, l10n, styling and tests for the initial reset password page
Closes #FXA-10475
Because:
* 'Start browsing' is confusing since it takes users to account settings
This commit:
* Updates the copy to 'Manage your account'
fixes FXA-10376
Because:
* We want to collapse the warning message on mobile by default to preserve real estate
This commit:
* Move the warning into a separate component
* Convert to use the details/summary elements
* Styling tweaks
* Copy updates to match latest design for complete reset password
* Remove unused old version of WarningMessage
Closes #FXA-10459
This commit:
* Tweaks the 'Signed in successfully' success banner image/spacing/conditional display
* Redirects signed-in desktop CAD users to /pair
* Redirects end flow of inline recovery key to /pair
* Updates some tests to waitForURL due to some local flakiness
fixes FXA-10466
Co-authored-by: Lauren Zugai <lauren@zugai.com>
Because:
* Reset password with code is now fully rolled out
This commit:
* Remove functional tests for reset password with link
* Remove config check for resetPasswordWithCode flag in functional-tests
* Remove content-server resetPasswordWithCode feature flag/env
* Remove auth-server passwordForgotOtp.enabled config
Closes #FXA-9728, FXA-10387
Because:
- We are improving UX
- Balloon UI pattern were problematic on mobile
- We have updated copy / mesaging about password resets
This Commit:
- Adds new components that dispay password criteria inline
- Removes info about passwords and encryption
- Adds in new copy informing users about password resets
- Updates tests to check for appropriate copy
Because:
* We are updating the design of the AccountRecoveryConfirmKey page
* We want to show the storage hint that users have had the option of saving
This commit:
* Update AccountRecoveryConfirmKey page content, l10n, stories, test
Closes #FXA-7894
Because:
* We want to encourage Sync signin users to create an account recovery key
This commit:
* Moves and refactors part of FlowRecoveryKeyHint into new component for sharing
* Sets ups the create recovery key and hint handlers in container component, call where needed
* Queries if recovery key exists after signin if sync, stores PW-related data into sensitiveDataClient
* Navigates signing in desktop Sync flow users without a recovery key to this new flow before taking them to CAD, if the feature flag is on
closes FXA-10079
Because:
- Locally the sync service wasn't running.
- We couldn't test sync flows against a local sync server
- There's a new version of the sync server that uses rust
This Commit:
- Sets up a dockerfile for syncstorage-rs that is tailored to fxa's local stack
- Updates pm2 sync job to run this docker container and initialize its databases.
- Updates firefox config/profile to point at this service
- Starts firefox up with the FIREFOX_DEBUGGER=true env.
- Useful for debugging sync
- Useful for debugging FxA web channel messages
Because:
* Accounts has its own dedicated help link we should use instead
* We want a metrics event for when users click on this link
This commit:
* Updates the link and adds the Glean event
closes FXA-10220, closes FXA-10221
Because:
- We noticed that some of the usage for webchannels was inconsistent.
- Of the web channel messages we send only FxAStatus and LinkAccount actually return responses.
This Commit:
- Removes implied response from the fxaLogin command that wasn't actually sent by firefox.
- Updates the functional tests to better reflect the actual commands and responses sent by firefox by creating some types. This should avoid mistakes