Skip to content

[bug] Double-post on SIWFv2 login callback #184

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JoeCap08055 opened this issue Mar 21, 2025 · 0 comments
Open

[bug] Double-post on SIWFv2 login callback #184

JoeCap08055 opened this issue Mar 21, 2025 · 0 comments
Labels
bug Something isn't working frontend

Comments

@JoeCap08055
Copy link
Contributor

JoeCap08055 commented Mar 21, 2025

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

  1. Navigate to SAT frontend
  2. "Signup/Login with Frequency v2"
  3. Go through signup/login flow, receive verification email
  4. Watch:
    • account-service-api logs
    • Browser dev tools "Network" tab in SAT frontend window
  5. 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)
@JoeCap08055 JoeCap08055 added bug Something isn't working frontend labels Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working frontend
Projects
None yet
Development

No branches or pull requests

1 participant