Login stopped working (JWT issues)

Help - Plug n Play
1

We are using the no-modal@5.1.0 SDK to authenticate users using google/linkedin with an aggregate verifier.

As of several hours ago login stopped working, this is what we’re seeing:

This graphql query fails with a 400 status code (fired from the page you maintain, shown during login):

image
image1126×199 28.5 KB

We see multiple errors on the console as well:

image
image951×1246 243 KB

From our logs we also see that the id token is missing in the token returned from the SDK:
image

Just to clarify:

  • We are using the no-modal SDK in a way that we take the result search parameter from the URL after the SDK redirects the browser back to our app. We know that contains the ID token which we then reuse
  • This setup was working this morning, we haven’t deployed anything on our end
  • We have a production app currently down because of it

Please advise

2

@shayg Thanks for reaching out.

Your issue has been forwarded to our Dev team and will be looked into on priority. We will get back with further updates once more information becomes available.

3

This might have happened because of migrations in the “mainnet” network. Can you please check if it’s still happening? Also please upgrade to the latest SDK v6 if possible. A lot of these errors have been solved in that. Here’s a guide on how to do it: PnP Modal SDK - v5 to v6 | Documentation | Web3Auth

4

We are using the cyan network, was it migrated as well?

Regardless, it’s still happening.

We are already working on upgrading but that will take a while, is there another solution you can provide us with?

We did notice that using the @web3auth/single-factor-auth library with similar configuration works, we are considering rebuilding the our auth mechanism as another alternative

Can This is a high priority issue for us which affects the entire company, can you give us an explanation?

5

This was not occuring on the cyan network, only mainnet.

SFA would be an alternative as yall suggest, but we’re digging further on this issue.

could you provide the endpoint failing here? or the network waterfall

6

The endpoint that fails is the graphql endpoint: https://api.openlogin.com/graphql.

However, it seems things are working again (the graphql endpoint but also the overall login), can you elaborate on the changes done on your end?

7

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