# Sporadic issue wp-discourse/SSO: Nonce has already expired

**URL:** https://meta.discourse.org/t/sporadic-issue-wp-discourse-sso-nonce-has-already-expired/94353
**Category:** WordPress
**Created:** [9 augustus 2018 om 21:13 UTC](https://meta.discourse.org/t/sporadic-issue-wp-discourse-sso-nonce-has-already-expired/94353 "2018-08-09T21:13:30Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![bekircem](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bekircem/32/44582_2.png) [@bekircem](https://meta.discourse.org/u/bekircem)
#### Post date: [9 augustus 2018 om 22:54 UTC](https://meta.discourse.org/t/sporadic-issue-wp-discourse-sso-nonce-has-already-expired/94353/3 "2018-08-09T22:54:51Z")

</div>

I used a similar method in several projects with lastest version of Wordpress and Discourse. I used Wordpress as SSO provider. It works correctly.

Are you using the standard Wordpress registration system? Custom functions on function.php can cause conflicts but it seems that your problem is not related to it. Also, you can check API and Webhooks.

After solving this problem you will probably need to be that:

> [@Auto activated accounts for WP Discourse SSO?](https://meta.discourse.org/t/auto-activated-accounts-for-wp-discourse-sso/90272/6):
>
> As long as users are not automatically logged in before responding to the password reset email, you can use this function. It will work without any changes: add\_filter( 'discourse\_email\_verification', 'wpdc\_custom\_disable\_email\_verification' ); function wpdc\_custom\_disable\_email\_verification() { return false; }

---

_[View the full topic](https://meta.discourse.org/t/sporadic-issue-wp-discourse-sso-nonce-has-already-expired/94353)._