James_Hope reports an issue with Discourse’s SSO integration using Firebase, where logs show “Nonce has already expired” despite following Discourse’s SSO setup instructions. The logs reveal two SSO attempts: one with an empty payload and another with valid user data (email, external_id, nonce, etc.), both failing due to expired nonces. pfaffman suggests checking server clock synchronization, but James_Hope confirms clocks are synced between the Discourse server and the SSO provider. In post 4, James shares the Java code used to generate the SSO redirect URL, including nonce encoding, Base64 payload, and HMAC-SHA256 signature generation, hoping to reveal the root cause. The issue remains unresolved as of cb-candor’s follow-up asking if a solution was found. The problem prevents users from logging in via SSO, impacting site usability.
Thanks for the suggestion but the clock doesn’t appear to be the issue. The discourse server and server from which the nonce is generated is on the same time.