A bug has been reported where after logging in, a “null” is added to the login URL, resulting in a 404 page. The issue occurs when logging in via social media (Facebook, Google, GitHub) and sometimes with regular login. Despite the 404 page, the user is actually logged in and everything works fine once they navigate away from the error page.
The bug has been consistently reproduced on try.discourse.org by multiple users (jomaxro, pmusaraj), but not on meta.discourse.org. The issue is thought to be related to a redirect issue, possibly caused by recent changes to SSO redirect back logic.
vinothkannans has fixed the issue with a commit to the discourse repository (commit). Users are advised to clear their cookies and test the social login flow to verify the fix.
I believe this started the last couple beta downloads, but now after logging in “null” is added to the login which takes you to a 404.
To reproduce:
Login via any mechanism (I’ve tried both facebook and regular user login)
Logout
Login again and you will get loginmethod/null (previous beta it was no slash just loginmethodnull) - such as: https://community.yinyanghouse.com/auth/facebook/null
You are actually logged in and everything works fine once you get away from the Oops not found page…
I’m assuming this is some sort of redirect that isn’t happening correctly, but just thought I would report…
I can’t seem to experience it on meta (but there I use my github account if that matters) - I can seem to get it everytime on my site https://community.yinyanghouse.com/ - at least with regular login and facebook…
@vinothkannans can you have an attempt to repro? I recall you recently changed some of the redirect back logic in the context of sso, maybe this is related
