Hello I'm trying to implement a custom SMTP configuration for passwordless auth as specified in this guide https://supertokens.com/docs/passwordless/email-delivery/smtp/configure-smtp . The problem though is that the init method from passwordless does not expect any parameter such as

emailDelivery

as specified in the above-linked article. Could you please help take a look at this? Type - Supertoken NodeJS Version - 11.3.0

Hey all, is there a way with Supertokens to handle account management ? I have multiple users with different roles (admin, user) linked to one account. These users can only retrieve data from entries linked to that account. Pretty common for B2B apps. How do you deal with that ? Thanks a lot

Has anyone found that when they're logged in with super tokens and the backend is verifying their ID, that after they move off the frontend tab for a bit and come back, the userId is rendered as null on the backend? But then when the frontend is refreshed, the userId is correctly set again

This is one of our components. We have multiple routes. My understanding was that in the if (sessionContext.loading === true) { return null; } if we changed the return null to a loader component, then we could display a loader between our routes but we are unable to see anything even when the route takes time to load. Is there a different way to show loaders?

Hey there, @rp_st I'm currently integrating social authentication (google) into my application via SuperTokens. I'm looking to retrieve additional user details such as first name, last name, and gender from the social authentication process. However, it seems that these details are not being populated in the user data. as these are basic user details that must provided by google or any other social auth. Could you please let me know if there's any extra configuration required in the SuperTokens config to fetch these details, or if it's outside the scope of SuperTokens?

Is it safe to set checkDatabase to false in verifySession for all endpoint if I am writing my own logic for checking revoked blacklisted tokens? What does supertokens core check apart from checking whether the token is blacklisted?

And if possible to have a “drop in replacement using OAuth” for what we have today, is there an architecture where: The user hits login -> redirect to a service that’s using SuperTokens+Jackson under the hood, they login, we issue an Access Token, RT/Cookie, and issue it to my front end? And then on the backend I can point it at a JWKS for a token verification?

I am just starting to work with supertokens. I prepared the project as in the tutorial for AWS lambda. I stopped at the 404 problem and prepared the frontend on this init: appInfo: { appName: "SuperTokens Demo App", apiDomain: "https://api.example.com", apiBasePath: "/auth", apiGatewayPath: "/", websiteDomain: "https://frontend.example.com", }, I prebuild UI and i works. When I try type email to sign up I see network issue: Request URL: https://api.example.com/auth/signup/email/exists?email=asda%40dsa.com Request Method: GET Status Code: 404 Not Found But when I opened this page I see response: {"status":"OK","exists":false} CORS works: Request URL: https://api.example.com/auth/signup/email/exists?email=asda%40dsa.com Request Method: OPTIONS Status Code: 200 OK I use the API GW V2 with integration for route: ANY /auth/{PROXY+}

I am trying to set debug: true in init, however typeInut doesn't have definition of debug. using supertokens-node 14.0.2

Setting up multiple frontends for one backend for python flask , what value of website domain to keep if we have multiple frontend consuming the same backend , will the origin thing work for python flask as well as mentioned in the docs @rp_st