If you visit https://discourse.fictiousexample.com/t/my-fine-topic/12345 and
login required is enabled, you’re redirected to https://discourse.fictiousexample.com/. Then you have to click the login button, and then you’re redirected back to the home page rather than the topic that you wanted in the first place.
What I would expect to happen (and what my client using auth0 wants to happen) is when you access a topic and are not logged in, you’d go straight tot the log in and be redirected to the topic after you’re logged in.
I thought at first it was a problem with GitHub - auth0/discourse-plugin: Discourse plugin to authenticate with auth0., but the problem seems to be with the
login required setting rather than the plugin.
This seems similar to the problem of trying to access a protected topic when you’re not logged in. What happens in that case is you get a 404 and are then on your own to log in and try again to access that URL.
Would it be possible to when hitting a route that is protected to give the user an opportunity to log in before giving up?