You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When SAT frontend receives a login/signup callback from Frequency Access, the SAT frontend appears to be sending the verification payload to the backend (and thence through to the Gateway Account Service) twice
Diagnostics/Steps to Reproduce
Navigate to SAT frontend
"Signup/Login with Frequency v2"
Go through signup/login flow, receive verification email
Watch:
account-service-api logs
Browser dev tools "Network" tab in SAT frontend window
Enter verification code from email
Expected Results
SAT frontend /login/callback route received ONCE
SAT frontend makes ONE call to SAT backend /auth/login/v2/siwf/verify
account-service-api receives ONE request at /v2/accounts/siwf with an authorizationCode from the callback
Actual Results:
SAT frontend /login/callback route received ONCE (seen in Network tab)
SAT frontend makes 2 calls to SAT backend /auth/login/v2/siwf/verify (seen in Network tab)
account-service-api receives 2 identical requests at /v2/accounts/siwf with the same authorizationCode (seen in logs)
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Description
When SAT frontend receives a login/signup callback from Frequency Access, the SAT frontend appears to be sending the verification payload to the backend (and thence through to the Gateway Account Service) twice
Diagnostics/Steps to Reproduce
account-service-api
logsExpected Results
/login/callback
route received ONCE/auth/login/v2/siwf/verify
account-service-api
receives ONE request at/v2/accounts/siwf
with anauthorizationCode
from the callbackActual Results:
/login/callback
route received ONCE (seen in Network tab)/auth/login/v2/siwf/verify
(seen in Network tab)account-service-api
receives 2 identical requests at/v2/accounts/siwf
with the sameauthorizationCode
(seen in logs)The text was updated successfully, but these errors were encountered: