# SSO incorrect nonce

**URL:** <https://meta.discourse.org/t/sso-incorrect-nonce/228925>\
**Category:** SSO\
**Created:** [June 3, 2022, 10:48am UTC](https://meta.discourse.org/t/sso-incorrect-nonce/228925 "2022-06-03T10:48:20Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Rikatemu](https://avatars.discourse-cdn.com/v4/letter/r/c57346/32.png) [@Rikatemu](https://meta.discourse.org/u/Rikatemu)\
**Post date:** [June 3, 2022, 10:48am UTC](https://meta.discourse.org/t/sso-incorrect-nonce/228925/1 "2022-06-03T10:48:20Z")

</div>

Hello,

I have a problem integrating the [Discourse Connect](https://meta.discourse.org/t/13045?silent=true) 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

> bm9uY2U9NzE1ZDE5MDM3YTUzZDY0ZDY4NTU3YjIyMzVmYmE4NzEmcmV0dXJuX3Nzb191cmw9aHR0cHMlM0ElMkYlMkZmb3J1bXMucGxheXJlc3BhcmsuY29tJTJGc2Vzc2lvbiUyRnNzb19sb2dpbg%3D%3D

which after decoding shows this nonce

> nonce=715d19037a53d64d68557b2235fba871

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.

---

_[View the full topic](https://meta.discourse.org/t/sso-incorrect-nonce/228925)._