SSO incorrect nonce


I have a problem integrating the Discourse Connect SSO solution.
Everything is up and running and all of the data I encode and decode seem correct.

The problem is that when I try to login I get a login error

Account login timed out, please try logging in again.

and on the /logs page I can see

Nonce is incorrect, was generated in a different browser session, or has expired

Weirdly when I start the SSO process the /logs page shows this nonce

nonce: 5bfe777da39abd9199ef213453975310

but in the redirect URL that leads to my login page the sso parameter is


which after decoding shows this nonce


therefore the nonce doesn’t match in the final payload.

Is this a bug or am I doing something wrong ?

Currently we are using the latest 2.9.0.beta4 version.

1 Like

I currently have this exact same problem, did you come to any sort of resolution?