Users are experiencing an ‘Expired Nonce’ error when accessing WordPress admin (/wp-admin/) after logging in via Discourse SSO, despite remaining in the same session. cmdntd reports the issue persists even after attempting a suggested fix involving wpdc_sso_client_querysimon, and rules out Cloudflare as the cause by bypassing it via page rules cmdntd. Interestingly, some SSO links (e.g., those with parameter ‘7’) still work, suggesting the SSO mechanism itself is partially functional cmdntd. Another user, Golaxo, encounters the same issue and confirms the suggested fix doesn’t resolve it Golaxo. After investigation, Golaxo identifies a conflict with the Paid Membership Pro plugin as the root cause, though content restriction for SSO users remains unresolved. angus had previously asked if Cloudflare was involved, but the issue appears unrelated to it. The thread highlights a session/nonce handling problem within the WordPress-Discourse SSO integration, potentially triggered by plugin conflicts or caching, and suggests further debugging beyond the initial workaround.
Hi, I use sso to login to wordpress by discourse. I used discourse wordpress plugin
First it’s work smoothly
But when I’m in the same session (not log out), and try to go to link admin /wp-admin/, it does not redirect me to dashboard, and show this error in login form:
Expired Nonce
There is something wrong with session or cookies
This make user confused, because I use sso by google login
I think the problem you are having is caused by object caching on your server. Try adding something like the following code to your WordPress theme’s functions.php file to see if that solves the problem:
Thanks mate, after swearing a lot I found the problem: the Paid Membership Pro plugin made a conflict. I still need to find out how to restrict content on Wordpress for users coming from Discourse SSO but at least I see where the problem is now