No call to the logout url for cognito is called, user is not properly logged out

This occurs when I followed the cognito guide.

I have 2 google accounts logged in on my device. When I login it gives me an option to pick which account I want to login w. I get a wallet address. When I log out, a call to https://session.web3auth.io/v2/store/set which I assume destroys the session on web3auth servers. Everything looks good so far.

However, when I try to switch my account, trying to login via 2nd account I no longer get an option. It just logs me into account 1 directly until the session expires on the cognito token. Ideally, it should also call the logout endpoint for cognito which would then log the user out properly and invalidate the cognito token as well. For reference I am using the implicit flow.

Edit: Nevermind, I missed the part in the guide where it says I have to call it manually. I was going off of what was there in the demo. Would be nice if that is also added to the demo.

Hi Aniket! Thanks for reaching out with your issue regarding the logout process with Cognito in the Web3Auth integration. Here’s a summary of the details you’ve provided, which will help our support team understand your situation better:

  • SDK Details: Help - Plug n Play
  • Issue: No call to the logout URL for Cognito is made; user is not properly logged out.
  • Details of the Issue: Following the Cognito guide, when logging out, a call to https://session.web3auth.io/v2/store/set occurs, but the Cognito logout endpoint isn’t called, preventing account switching.

To better assist you, could you please provide the following additional details:

  1. SDK Version Number: (If available)
  2. Platform: (e.g., Web, Mobile)
  3. Web3Auth Initialization & Login Code Snippets: (If applicable)
  4. Any Browser Console Screenshots: (If you have them)

Once we have this information, a support team member will be able to look into it more closely for you. In the meantime, have you tried clearing the session or token on the Cognito side manually as a temporary workaround?

Looking forward to your response!

Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.