Benutzer werden nach erfolgreichem Login nicht zur ursprünglichen Seite umgeleitet

dax · 14. August 2025 um 12:53

Korrektur in:

github.com/discourse/discourse

FIX: redirect to 'private' topic when using discourse connect

main ← fix-redirect-when-using-discourse-connect

opened 03:45PM - 08 Aug 25 UTC

ZogStriP

+102 -18

When an "anon" user visits a topic that is "private", they will get a page that …is server-rendered and doesn't load the client-side app. When they click the "login" button, it will redirect to the /login route which loads the app. The only way we can know where the user landed initially is via the "document.referrer". The issue was that the code that checked the referrer was **after** the code that is doing the redirection to discourse connect. By putting the code before doing the redirection to discourse connect, we are successfully redirected to the landing url after doing the discourse connect auth. I've also added a system spec that test the happy path by starting the most basic discourse connect compliant sso server in the background.

Thema		Antworten	Aufrufe
Desired URL lost if `login required` is enabled and social logins are used Bug	5	1166	3. Januar 2018
On a private forum, a link to a topic sends them to the home page instead of the topic when they have to log in Feature	5	1048	26. März 2015
Discourse doesn't redirect to return_sso_url after user logs in on private site Support	4	4163	4. Oktober 2018
New Topic URL - Lost if not logged in Support	7	1898	5. Dezember 2015
Create a DiscourseConnect login link Integrations sso , discourseconnect , how-to	6	6388	25. September 2024

Benutzer werden nach erfolgreichem Login nicht zur ursprünglichen Seite umgeleitet

Verwandte Themen