What’s the time limit you would like to make?

something like a couple days or a week

I see. Ok

So I got my user located in MongoDb, when my user is logged in how can I call a function to get my user in MongoDb?

So how can I detect when my user becomes logged in?

Hey @User , regarding to check whether a user is logged in or not, you can use the

verifySession

middleware. You can check the details here: https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/sessions/session-verification

I'm looking for something for the frontend

So I'm waiting for a user to log in, when they do I get there user-id.

So how can I detect when a user is logged in on the front-end?

That would be after signin or signup API is called. You can refer to this to know how to handle signin/signup events on the frontend: https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/handling-signinup-success#2-handling-signin--signup-event-on-the-frontend

But what happens if they came back to the site that function would not fire?

You can use

useSessionContext()

or

Session.doesSessionExist()

in that case: https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/sessions/checking-session-front-end

hmm, how do we verify supertoken sessions over websockets? 🤔 which cookie(s) (or token?) should we pass and what method should we use in the node sdk?

Hi @User, we use cookies to authenticate a user. I think, the way you can authenticate a user via websocket is during the on connection event where the request object is available (I've checked this for ws library). If an active user session is present, the required cookies will be present in the request headers given that your API server and websocket server are on same domain. But the getSession function of node lib (https://supertokens.io/docs/nodejs/session/getsession) takes express request and express response object as parameter. So I'm not sure if it can be done that easily. You can use express-ws so the request will be of type express.Request. For response, you can create a dummy response of type express.Response. I suggest you create an issue regarding this in supertokens-node library

Is there anyway to see when the user is updated in Supertokens?

Kind of like how Firebase base has "onAuthStateChanged"?

@User for socket connections, you need to do session verification only when creating a socket connection. After the connection is established, you don't need to rely on session verification and can simply trust the socked connection.

@User we give you the ability to add post sign in / sign up and signout logic. Using those, you can know if a user is logged in or not. You can add logic there using our override API feature.

You can use something like socket-io middlewares for the same, it will help keep the session up to date. So even if the user revokes the session while the socket connection is still connected, he wont be able to access that resource

@kakashi_44 @rp @relentless , thanks for the answers, I'm using apollo graphql subscriptions for more context. Guess I'll have to figure out first if I can utilize the getSession function from the sdk

You can create a middleware that does session verification with the

sessionRequired: false

(See https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/sessions/session-verification#optional-session-verification) This would be applied to all requests from your apollo client. Then in you graphql server, maybe you could somehow check if

req.session !== undefined

?

I'm not entirely sure how it would work since we dont have a with-graphql example yet. But i'm sure that it would be possible.

yeah, should've been straight-forward in concept, I'm trying to figure out how to extract the req and res object from apollo subscription server's abstraction so I can pass it to supertokens' getSession function 🤔

well rip, can only get

req

, any other alternatives?

or rather, the lib doesn't expose it on the lifecycle events it supports 🤦‍♂️

hmm. How about using a different middleware for session verification only? Like I said before.. this won't require you to extract the

res

object at all from graphql.. only the

req

object - which you seem to be able to get,

Am I misunderstanding?

yes I can get the req a bit of implementation details but I can get the req object via the

onConnect

https://github.com/apollographql/subscriptions-transport-ws#subscriptionserver not quite sure where to plug the middleware tho 🤔

on Apollo Server 3, the subscription server has been separated