Problema esporádico wp-discourse/SSO: Nonce ya expiró

Soporte 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

Encontré el mismo problema después de realizar una copia de seguridad de la instancia de EC2 en ejecución y volver a lanzarla.

El nonce depende de que el valor esté establecido en Redis y en la sesión para la validación de CSRF.

Desactivé SiteSetting.discourse_connect_csrf_protection, lo que hizo que el inicio de sesión funcionara de manera consistente, pero aún no he depurado por qué la sesión no se está configurando correctamente.