Problème sporadique wp-discourse/SSO : le nonce a déjà expiré

Soutien WordPress
22

I adding some more to my debugging input so I could inspect the $sso_params passed into the sync_sso in an existing user case (success) versus new user case (failure), they both look similar. They both show properly filled out values for all these:

[avatar_force_update]
[avatar_url
[bio]
[name]
[require_activation]
[email]
[username]
[external_id]

What’s also head-scratching is that we have another very similar WordPress/Discourse installation and this doesn’t happen at all there. I’m going to pore over all the Discourse settings for each and see if there any differences that might be causing this.

23

I compared the settings for each of our Discourse forums and they are virtually the same. Thanks @RGJ for the help here. You guys are always very helpful. And luckily we hardly have any issues due to your good hosting. I’m sure we’ll track this down.

24

J’ai rencontré le même problème après avoir effectué une sauvegarde de l’instance EC2 en cours d’exécution et la relancer.

Le nonce dépend de la valeur définie dans Redis et dans la session pour la validation CSRF.

J’ai désactivé SiteSetting.discourse_connect_csrf_protection, ce qui a permis à la connexion de fonctionner de manière cohérente, mais je n’ai pas encore débogué pourquoi la session n’est pas définie correctement.