# SSO werkt niet meer 🤔

**URL:** <https://meta.discourse.org/t/sso-stopped-working/183813>\
**Category:** SSO\
**Created:** [19 maart 2021 om 21:44 UTC](https://meta.discourse.org/t/sso-stopped-working/183813 "2021-03-19T21:44:20Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![OlivierLambert](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/olivierlambert/32/209897_2.png) [@OlivierLambert](https://meta.discourse.org/u/OlivierLambert)\
**Post date:** [19 maart 2021 om 21:44 UTC](https://meta.discourse.org/t/sso-stopped-working/183813/1 "2021-03-19T21:44:21Z")

</div>

Hey guys!

I’m processing the SSO authentication in my PHP backend. I start by sending a curl request to my SSO URL ([Communauté et formation pour entrepreneurs](https://forum.latranchee.com/session/sso)) so I can get the SSO Payload and SIG, then proceed to create my own payload to create the proper redirect url.

Here’s where it gets weird…

If I access [Communauté et formation pour entrepreneurs](https://forum.latranchee.com/session/sso) in my browser, copy/paste the SSO and SIG into my script, the final redirect URL will work.

If I get it through CURL, the final redirect will show an error message and I’ll have this in my log:

```plaintext
Verbose SSO log: Nonce has already expired

```

I’m at a loss here… The problem seemed to have appeared out of no where and now my users can’t log in.

Did discourse change something to prevent bots from pigning /session/sso?

---

_[View the full topic](https://meta.discourse.org/t/sso-stopped-working/183813)._
