I just realized my SSO is broken, but I don’t know when it broke (possibly when updating from beta3 to beta4?). Nothing has changed AFAIK on the SSO side.
When I click on Log In it redirects to the SSO site correctly, sign-in works there, but the final redirect to Discourse fails: I get a blank page that just says “Error updating information, contact site admin” (the response headers indicate a 500 error). The logs in the admin interface are completely empty.
I can’t confirm it’s beta3 to beta4 as the community site hasn’t been launched yet, so almost no one is using it. It was working a few days back as there was one new user who signed in though.
After more investigation, the issue seems to be related to CloudFlare which I have enabled for the domain that hosts discourse. I paused CloudFlare and the issue seemed to have gone away.
Another thing: even if CloudFlare is enabled, SSO works if I reload the redirect URL after replacing the hostname forums.gitup.co by the raw server IP 54.68.80.84 in it e.g.
I think I fixed the issue: I noticed randomly this morning that Discourse had automatically added to the list of blocked IP addresses one of the CloudFlare IP addresses. I removed this block then explicitly whitelisted all their IPs. Then I reenabled CloudFlare, waited a few hours, and login with SSO appears to work again
