What is the key that SuperTokens use to sign access tokens ? I need to provide it to mongodb form some JWT verifications purposes.

We have used thirdpartyemailpassword and email verification recipes together, the users can either login with email password or third party probiders such as Google, Azure, okta, etc. Is there any way to find which login method the user logged in with?

Hi could I get some assistance? I am working on a feature where I want to send a link as part of a confirmation email. I would like to create a magic link that authenticates a user and allows them to cancel a booking. I have been looking at this documentation https://supertokens.com/docs/thirdpartypasswordless/custom-ui/login-magic-link but I don’t necessarily want the email to be sent automatically as we have a trigger through Salesforce Marketing Cloud and I would to pass in a token as part of this magic link. But I am not sure how to proceed. Any advice would be appreciated.

Custom Error Conditions on Sign Up. I'm adding an additional username field on account creation and saving that along with the userid, and email to my app db (separate from supertoken db). What I'm trying to figure out is if there is a prescribed way of handling errors in this scenario, and rolling back the entire creation on failure. I override emailPasswordSignUpPOST, to get the fields and persist, but how do I rollback transaction in event there is some error thrown by my custom logic

Hi everyone, I'm coming from Keycloak, i have some questions about SuperTokens. First, SuperTokens core doesn't have a administration console like in Keycloak? Second, we are work in a new web application with our own login UI, i can list the tenents after the login?

What would be the correct way to verify a session without the client accessing the API? I need to use PHP to get the token then verify it through the API instead of the client directly communicating with the API

Is there any update on mongodb support?

One more question: yesterday I tried to do such kind of implementation:

<SessionAuth 
      onSessionExpired={() => {
        console.log('AdminRoute onSessionExpired')
        navigate(RoutePaths.Onboarding)
      }} requireAuth={true}>
          {props.children}
      </SessionAuth>

to protect one of my FE routes, we don't use the built-in UI but the onSessionExpired is not being fired in case there is no session. I have tried to look through the react lib code and I found one code that tests the onSessionExpired prop but it also specifies requieredAuth={false} which doesn't make sense... do I miss something?

I was working supertokens with React and Django rest framework. I have added super tokens for both react and Django rest framework but I can't sign up or sign in. When I click sign up with Google it says "Something went wrong. Please try again.". And here is the error message : "GET /auth/authorisationurl?thirdPartyId=google&redirectURIOnProviderDashboard=http%3A%2F%2Flocalhost%3A3000%2Fcallback%2Fgoogle HTTP/1.1" 200 281. can you guys help me

We've got a problem with Supertokens on Node. Specifically usage with Fastify. I think your default error handler probably is not done right for Fastify (I may be mistaken). But the problem is that on token refresh, if you open a page like 2 hours of inactivity we get an error that kills the server instance completely. Here are some screenshots that I was able to collect from my colleague. Obviously, since the server dies after that, everything else stops working too throwing 500. Will try to debug further, but with the error handler that you guys provide it fails. Removing it and using a default Fastify that has internally doesn't change anything. Weirdly.