In a multitenant environment, I'm trying to use "getAuthorisationURLWithQueryParamsAndSetState(thirdPartyId, frontendRedirectURI) method" to get thirdparty login url, I'm having multiple tenants including public tenant. Public tenant don't have active-directory provider. But the other tenants have it. When I use that method, it's checking the public tenant. I'm using for logging in. I can pass tenant id from the front-end, but that method is not having a parameter to accept the tenant id. I'm struck here. Please help me out with this.

Hi, is it possible to get email from the session like user_id? session: SessionContainer = request.supertokens user_id = session.get_user_id() email = session.get_email()

When will Supertokens support MPC or Web3 auth? Google was saying its in Beta but I can't find anything

I'm getting 401 not authorized when using verifySession() in an express handler: app.get("/api/market/list", verifySession(), rateLimiter, asyncHandler(async (req, res) => { This is across subdomains. I'm calling domainname.com/api/thingy from dev.domainname.com Any ideas on how to fix that?

Hi, I'm trying to implement supertokens with out ldap and AD servers. From my understanding I need to implement a custom provider. I'm just not sure from the example code given how that works? How do we get the client id and client secret?

Hi, I have a problem with the Session.sighout function. After calling Session.signOut, the session still exists (Session.Session.doesSessionExist returns true). This is the code of my signout function:

javascript
await Session.signOut();
alert(await Session.doesSessionExist())

I am using the supertokens web sdk. Is there anything i did wrong?

Hi, this is the most #603466164219281433 channel I can see. I just wanted to say I'm giving supertokens a look. My stack is nextjs 13 / react 18. I believe there are no real examples of supertokens using the new nextjs 13 app/ directory (vs. pages/), but plenty of libraries require the migration, not just supertokens. Hopefully that part won't be as difficult as what I expect to be the difficult part, which is configuring supertokens and understanding what I'm doing. I will say though that I chose supertokens after looking for days at all the alternatives. Because 1) you're very explicit about your algorithm (access and refresh tokens), 2) you support username/password, and 3) you have a free open source self-host option.

Is there a way to get ip address from userContext? Trying to get user ip address when overriding sign up function

For oauth and email password, if someone sign up with different auth providers with same email, is this counted as different accounts? What about if they sign up with email then sign in with their oauth provider email that’s same? Curious what’s recommended behavior here and what flexibility I have

Hello team! We are an enterprise company currently developing a highly sensitive project with some financial institutions. Our requirement is to implement this hashing algorithm for all the users that are registered on our platform. We are using FastAPI for the backend so would appreciate any help.