In a discussion titled “SSO Stopped working ” under the SSO category, OlivierLambert reports that their PHP backend’s SSO authentication stopped working after fetching the SSO payload and SIG via cURL — resulting in a “Nonce has already expired” error. The issue arose unexpectedly and prevents users from logging in. simon explains that Discourse now ties the SSO nonce to the user’s session, meaning the user must directly visit /session/sso (via click or redirect) for the nonce to be valid — not fetched programmatically via cURL or Axios. OlivierLambert confirms they’ve adapted by redirecting users directly, but this breaks their preferred asynchronous login flow. They’ve also tested Axios (client-side) without success and ask for suggestions to restore async login while complying with the new nonce behavior. They thank simon for the clarification.
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:
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.
That’s what I’ve had to do to fix the issue, but that breaks my asynchronous login process. I really liked doing things that way.
I’ve also tried doing it through Axios. I would’ve expected it to work since the request is coming from the client. It doesn’t seem to be working either.
If you think of a way I could implement an asynchronous login process, I would welcome any tips! In any case, thank you for the response, greatly appreciated.