A user reported a bug in Discourse 3.6.0.beta1-dev where the Discourse Connect Provider login redirect fails, sending users to the forum instead of the intended return URL. The issue, which began around May after an update to 3.5.0.beta5-dev, was traced to a commit affecting login redirects. The user confirmed the problem was resolved after updating to the latest version, v3.6.0.beta1, which included a fix. uckelman identified the issue, christo provided the resolution, and uckelman confirmed the fix worked.
The non-Discourse parts of my site use the Discourse Connect Provider for logins. I noticed yesterday that the Discourse login page no longer redirects back to the page the user came from. Instead, a successful login redirects to our forum. We haven’t changed what we send Discourse’s /session/sso_provider endpoint since May, and the return_sso_url we set in the request payload looks to me like what we’re intending to be there.
I’m using Discourse 3.6.0.beta1-dev. I don’t know when the problem started, as logging out isn’t something I do myself very often. We have updated Discourse several times since May, which makes me wonder if I’m seeing a regression.
I’ve switched this over to the bug category as I’m now fairly sure this is in fact a bug in Discourse.
These two posts replying to the instructions for setting up Discourse Connect describe the same problem I’m having:
The first of those two posts has the problem staring after updating to 3.5.0.beta5-dev in late May. I had already identified the problem as starting for us no earlier than May, which I suspect is not coincidental.
