Because:
* There's an error case some users experience where it appears a client-side OTP code check is valid but our server then rejects it. We mishandle the error state and tell the user 2FA setup was successful
This commit:
* Updates our front-end OTP check in fxa-settings to use the same library our backend uses (otplib, but for the browser)
* Has auth-server throw an error if the TOTP code is invalid during set up, and handles it properly in the front-end by checking for an error, not updating apollo cache to show a successful TOTP setup if there is an error, and displays an error for the user
closes FXA-12035
Because:
* We want to incorporate the fxa-crypto-relier library into the Firefox
Accounts codebase and deprecated its webextension functionality.
This commit:
* Adds the fxa-crypto-relier library to the Firefox Accounts codebase.
Closes FXA-9741
Because:
* We want to reduce the dependencies in fxa-jwtool and bring more
of the functionality into the monorepo.
This commit:
* Moves and updates the fxa-jwtool code to function the same
except as TypeScript with classes and no additional dependencies.
Because:
* Ensure all localization strings can be localized in React Server
Components.
This commit:
* Removes LocalizerServer
* Adds LocalizerRSC to serve as a wrapper for ReactLocalization that can
be used by React Server Components, as well as a few other utility
methods.
* Adds LocalizerRscFactory that instantiates LocalizerRSC only with
bundles for a provided acceptLanguage string.
* Adds LocalizerRscFactoryProvider to be used with the NestApp to
instantiate and then intialize the LocalizerRscFactory. Initalization
will fetch all messages from disk and populate the bundles.
* Reorganize shared/l10n library to match Node style guide
* Removes demo l10n code
* Update purchase-details, terms-and-service components, and success and
error pages to use new LocalizerRSC class for localization.
* Adds temporary l10n-convert script to provide translation for existing
ftl strings.
Closes #FXA-8822
Because:
* We want to introduce nx to the repository
This commit:
* Adds nx with working builds
Closes: FXA-7341
Co-authored-by: dschom <dschomburg@mozilla.com>
Because:
* New routes and some account cleanup is needed for allowing a new
account with no password. This requires multiple re-usable functions
to be extracted from the existing create account handler.
This commit:
* Converts the account.js file to TypeScript and refactors the handlers
into a class to make room for the new account creation route.
Ref #8735
Because:
* We are using NestJS for application architecture on new projects.
This commit:
* Moves the event-broker to a NestJS architecture.
Closes#6238
- We have two clients for the auth-server API, one in `content-server/app/scripts/lib/auth` and `fxa-js-client`. The content-server one was meant to replace fxa-js-client but I didn't finish the work to get it running on nodejs.
- Extracts the content-server implementation into `fxa-auth-client`
- Wraps the implementation with shims to work with nodejs in `server.ts`
- Updates references to fxa-js-client to use fxa-auth-client
- Removes fxa-js-client
Because:
* The gql-api needs the ability to issue new recovery codes and
update the users two-factor auth settings.
This commit:
* Add's two-factor auth and recovery code mutations.
Closes#5395
Because:
* We want to alter/update the profile avatar/displayname and modify
email addresses in use.
This commit:
* Add's mutations to upload an avatar, change the display name, and
manipulate email addresses in use.
Closes#5397, #5396
To reduce duplication and encourage consistency in our
typescript builds this extracts most of the options
into two base configs, one for node and one for browsers.
Also, in order to better utilize workspaces the require
paths to fxa-shared and fxa-react were updated throughout.
