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

제품 지원 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는 CSRF 검증 시 Redis와 세션에 값이 설정되어 있어야 합니다.

SiteSetting.discourse_connect_csrf_protection을 비활성화하니 로그인이 일관되게 작동했지만, 세션이 제대로 설정되지 않는 이유는 아직 디버깅하지 못했습니다.