偶发问题 wp-discourse/SSO：Nonce 已过期

支持 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

我在对运行的 Ec2 实例进行备份并重新启动后遇到了同样的问题。

nonce 依赖于在 redis 和 session 中设置值以进行 csrf 验证。

我关闭了 SiteSetting.discourse_connect_csrf_protection，这使得登录能够稳定工作，但我尚未调试出 session 为何未能正确设置。