What is the name of the domain?
What is the error number?
None
What is the error message?
None
What is the issue you’re encountering
SSO being prevented by Cloudflare
What steps have you taken to resolve the issue?
Paused and unpaused Cloudflare to verify the issue only happens when CF is enabled. Walked through the SSO code to verify it is working correctly as it has for many years.
What are the steps to reproduce the issue?
I recently placed my client’s site www.augi.com and its subdomain forums.augi.com under Cloudflare’s protection. In general CF has been excellent at blocking unnecessary and suspicious traffic as we had hoped.
www uses a content management system for member registration, subscriptions, login, logout, etc. forums is setup to allow single sign on via the login functions of www. So, once registered and activated, members will login at www and if successful, are logged in to both the content management system at www and the forum software at forums.augi.com. This has been working great for many years. Login is accomplished via a custom plugin for the content management system and uses a combination of cookies that are set at the top level domain (.augi.com) and session info stored in the two applications’ database tables. Again, never an issue with this over many years.
Once we began using CF, I noticed that logging into the content management system works fine, but the SSO login does not happen in the forum software. I did some testing and found that when login occurs via the content management system, as usual, the appropriate cookies and database session info are all created and present in both systems. So it seems like login should be happening in both systems.
When I “Pause Cloudflare”, the full login process works. When I “Unpause Cloudflare”, the issue shows up again. I thought there might be some caching going on within CF, but when I “Bypass Cache for Everything” and purged it, there was no change in the issue.
I am not using CF Access, this is the application level login. Any ideas what may be causing the issue?