Production “invalid signature” error with `@dfinity/auth-client`

We have seen a few instances of an “Invalid signature” error pop up on our production domains recently. We’ve seen this locally before (caused by identities being stored from old replicas, forum post) …but seeing this in prod is new, and I’m not sure what could be causing the issue.

We haven’t been able to reproduce it ourselves, but we’ve heard that wiping out indexeddb does fix the issue. Has anyone experienced this issue before, and perhaps found the cause?

It started recently with (seemingly) no obvious commits in our identity provider code to point to as a root cause. We’ve been using basically the same agent-js / @dfinity/auth-client powered auth code for several years. :thinking:

Invalid signature: Invalid basic signature: EcdsaP256 signature could not be verified: public key 0418...f79b, signature 480f...cd87, error: verification failed

Are you using agent-js 2.1.3 or 2.2.0?

Those are known versions that could have signature issues on retries.

1 Like

Interesting that those versions have known signature issue. I’m on 1.2.0. Might be time to bump versions.