PART 1: feat(auth): Add backend APIs needed to move off GraphQL #19979
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 tasks
- Add consolidated GET /account endpoint that returns all account data in one call - Add POST /account/email_bounce_status endpoint - Add POST /account/metrics_opt endpoint for telemetry opt-in/out - Add metricsOpt(), emailBounceStatus(), and expanded account() methods to auth-client - Add DEPRECATED_KEYS to content-server account model to handle new localStorage keys from fxa-settings Part of: FXA-12993
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because
fxa-graphql-apiserver is being removed, andfxa-settingsneeds direct REST API equivalents for data it currently fetches via GraphQL/accountendpoint returned only subscription data, butfxa-settingsneeds account metadata, 2FA status, recovery key info, linked accounts, and security events in a single callThis pull request
/account/email_bounce_statusendpoint to check for hard email bounces (with alias normalization support)/account/metrics_optendpoint to set metrics opt-in/opt-out stateGET /accountto returncreatedAt,passwordCreatedAt,hasPassword,emails,linkedAccounts,totp,backupCodes,recoveryKey,recoveryPhone,securityEvents, andmetricsOptOutAtemailBounceStatus,metricsOpt) tofxa-auth-clientemailBounceStatusCheckrate limit rule torate-limit-rules.txtfxa-content-serveraccount model to handle new fields via deprecated keys listIssue
Closes: https://mozilla-hub.atlassian.net/browse/FXA-12993
Checklist
Other Information