integration
Because:
- We explicitly capture an exception for oauth-web-integrations and
send it to Sentry, then throw for the app/index to redner correct
component
- And we capture and send the error to Sentry again
This Commit:
- Removes the double Sentry logging
- Adds some more details to captured exception to track down cause of
error
Closes: FXA-12088
Because:
- The refresh button for connected services doesn't re-enabled when the
request finishes
This commit:
- Adds a useState to track the refresh status for connected-services,
enabling/disabling the button as necessary.
- Adds tests for the new functionality
Closes: FXA-3454
Because:
- We have some routes that still call to the old customs server
- And an edge case where a route will error when trying to access the
Redis cache
This Commit:
- Updates the old customs check to noop to keep scope and changes
limited but also supress error
Closes: FXA-11299
Because:
* We were handling sending this in the front-end, and since VPN uses our account/login endpoint, they were not receiving the session verified email
This commit:
* Removes the front-end checks and adjusts email sending logic to not send the session verification email unless the RP is VPN or is requesting keys
fixes FXA-12647
This commit:
* Reverts a previous reversion we did for 'refactor(sessions): Separate 'verified' into 'emailVerified' + 'sessionVerified', other clean up' as well as a follow up 'fix(api): Return 'verified' from 'account/login''
* Introduces clarity by separating 'verified' into 'sessionVerified' and 'emailVerified' across relevant endpoints
* Removes/reduces checks of verificationTokenId and/or tokenVerified to just tokenVerified, as these both check verificationTokenId and was unclear
* Fixes a case where auth-server is returning 'verified: true' for a non-2FA non-Sync unverified session, and removes corresponding front-end bandaid fixes
* Removes an env var previously added for testing that we don't need, updates docs for another covering that case
Because:
* We had an issue with VPN not receiving a login email despite verified: false, because we are skipping non-2FA non-Sync sign-in verifications (this case) for RPs, but since VPN manages their own UI they cannot skip this page when verified: false, so we reverted it temporarily
* We have had confusion around unverified sessions and the 'verified' flag
* We've introduced a band-aid fix in the front-end
originally closed FXA-12454 / FXA-12646
This pull request
- Updates getCardIcon util to return width and height of icon
- Updates type in DefaultPaymentMethod from PaymentProvidersType to SubPlatPaymentMethodType
- Refactors Payment method section in SubMan page
- Displays error if expired payment method or account issue
Closes PSY-3350
robust
Because:
- We've seen tests have issues during the cleanup
This Commit:
- Splits out the large destroyAllAccounts call to make it more
managable
- And, defaults to always fetching a new session token instead of
relying on the token in "cache"
Because:
* We want to know if passkey support is sufficient to justify implementation
This commit:
* Adds a glean event to sample capability support for passkey/WebAuthn, including PRF (Pseudo-Random Function) extension support and minimal device data.
* Adds a helper function to collect the data and emit the event.
Closes #FXA-12640
This commit:
* Renders third party auth buttons for service=aimode and service=relay when the capability is set
* Renames 'useSyncEngines' to 'useFxAStatus' and passes back the capability status
* Includes navigation handling to support these flows including new or existing account third party auth sign-in with or without 2FA
* Sends empty oauth data to the browser to signify end of the login flow
* Adjusts can_link_account web channel sending
* Adjusts account/status with session token endpoint to return 'hasPassword'
Because:
* We want to allow third party auth sign-ins and sign-ups for service=aimode and service=relay OAuthNative integrations
closes FXA-12540
closes FXA-12377
Because:
* We split this into two values in another PR, but at least one other team relies on this value
This commit:
* Adds the field back and marks it as deprecated
Because:
* We will need to keep track of whether a customer is eligible to redeem a churn coupon when checking if the customer’s redemption count is less than the redemption limit set for the churn content in Strapi.
This commit:
* Creates a repository for ChurnIntervention
* Adds Action to return Churn Intervention data
*(BOTH STILL IPR)
Closes #PAY-3359
Because:
- PayPal button used in Subscription Management has the client ID hard
coded to sb instead of using the client ID set in env vars.
This commit:
- Updates PayPal button used in Subscription Management to initialize
with env var client ID.
Closes #
Because:
- Need to enable experiments in payments-next by adding support for
nimbus.
This commit:
- Initializes the experiments shared library
- Updates subplat backend glean metrics with nimbus_user_id
- Adds Nimbus client
Closes #PAY-3248
Because:
* We have had confusion around unverified sessions and the 'verified' flag
* We've introduced a band-aid fix in the front-end
This commit:
* Introduces clarity by separating 'verified' into 'sessionVerified' and 'emailVerified' across relevant endpoints
* Removes/reduces checks of verificationTokenId and/or tokenVerified to just tokenVerified, as these both check verificationTokenId and was unclear
* Fixes a case where auth-server is returning 'verified: true' for a non-2FA non-Sync unverified session, and removes corresponding front-end bandaid fixes
* Removes an env var previously added for testing that we don't need, updates docs for another covering that case
closes FXA-12454
