# 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:** 2

<div class="post-metadata">

**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\
**Post date:** [22 maart 2021 om 17:15 UTC](https://meta.discourse.org/t/sso-stopped-working/183813/2 "2021-03-22T17:15:59Z")

</div>

> [@OlivierLambert](#):
>
> Did discourse change something to prevent bots from pigning /session/sso?

Yes, the `nonce` is now attached to the session of the user that it was generated for. It looks like the problem you are having is related to this:

> [@OlivierLambert](#):
>
> 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

Instead of making a curl request, the expectation is that the user who is to be authenticated will visit `/session/sso`, either by clicking the site’s Log In button, or by being redirected to `/session/sso` from your application. When they do that, they will be redirected back to your application by Discourse. The `nonce` that is found in that payload will be valid.

---

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