Is there an endpoint to check if a user is logged in


(Jay Pfaffman) #1

I need a URL that will return 200 for a logged in user and 401 or 403 if the user is not logged in.

If require_login is checked, every page does a 301 to the login page.


(Dean Taylor) #2

Is this a user request, i.e. using the current users session?

Or…

Is this an admin API request using an admin API key?


(Jay Pfaffman) #3

Yeah. It’s me not understanding the question I’m asking.

I’m trying to do an auth_request in NGINX to tell whether the request is coming from a user that’s logged in by querying an URL to see whether it gets a 200 response or not.

It’s occurring to me that doing that is not quite as simple as I’d hoped.


(Dean Taylor) #4

You could try /session/current.json

It will return 200 if authenticated and 404 if not.

Generally .json / API requests don’t redirect.


(Jay Pfaffman) #5

That seems promising. I’ll keep poking at it.

Many thanks!


(Josh) #6

Is there an easy way to do this from a different subdomain?

Example, the forum is at forum.example.com and the request is coming from example.com (either from the frontend or backend code).


(Jay Pfaffman) #7

Sure. You can make an API call from anywhere.


(Michael - DiscourseHosting.com) #8

But this specific call needs to be done from the frontend, since it will use the session cookies sent by the browser to the forum.


(Josh) #9

The Discourse session cookie appears to be just for the subdomain, so would the cookie be accessible from the top-level domain? I see _forum_session on the Discourse subdomain but it doesn’t appear when visiting the TLD.

If the cookie were available on the top-level domain, I was thinking that it would also be passed to the backend, so the backend could forward it to Discourse, but I’m not sure.

Maybe it requires using Discourse as an SSO provider? If it isn’t known whether the user is logged in, then we could redirect through the SSO process to check. I’m currently setting it up on a test server to see if it would work.

Edit: my end goal is to generate a JWT with the user data from Discourse (only if logged in to Discourse) and pass it to Firebase. There is a Discourse server on the subdomain, an extra backend server that can perform additional logic, and an SPA that connects to Firebase if given a JWT.


(Sam Saffron) #10

If you want anything fancy like this you would need to implement your own CurrentUserProvider


(Josh) #11

Thanks, I just looked it up and found this other thread, so I’ll ask some more questions about it over there.

Edit: it looks like we can do what we need with Discourse as an SSO provider.


(Sam Saffron) #12

If you can do it with SSO I highly recommend you go that path vs a provider


(Josh) #13

Thanks, it looks like we can check if a user is logged in and then redirect through Discourse’s SSO route if not logged in. It seems to work well on my laptop. The user logout webhook from Discourse can then log them out of the other app.