Hi 🙂 After reading the docs, I'm unsure what to do in my use case. I have a social login set up in nextjs, and I would like to send the provider refresh token to my backend API (different service). I already extracted the refresh token in the backend config

override.functions.signInUp

section. I need to make an authenticated call to my backend with the current user. Since I don't have a session in the

override.functions.signInUp

function, I'm unsure how to proceed. Will appreciate your help 🙏

I have a question about the Dashboard - is it safe and meant to be deployed in a production? I'm currently using a self-hosted instance, and what sparked this question for me is that self-hosted doesn't require sending the

api-key

header, thus allowing anyone who has access to the supertokens instance to create a new user/change password etc. My assumption is that supertokens instance should not be exposed to the world, and communicated only with via backend. Is that correct?

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 running NextJS with an Express API on a separate server. Is there a way for me to get the user session inside getServerSideProps in my NextJS application? I have tried following the NextJS specific directions for getServerSideProps but it always comes back unauthorized. Any advice? I'm thinking I need to use the SDK inside getServerSideProps which is fine but how do I get the user id or session id so I can check if they have a valid session? My goal is to redirect to a different page if the user is authenticated. My api is running on api.example.com and app on app.example.com on my localhost by adjusting my etc/hosts. I get a session on first page load after logging in, if I refresh the page then it fails with the UNAUTHORIZED error triggering an infinite refreshing loop.

How many parallel logins can a supertokens core and supertokens node can handle in a single core server?

Hi, I'm trying to setup the dashboard. I'm trying to create a user using the CLI command but I'm getting

{"status":"INVALID_EMAIL_ERROR"}

curl --location --request POST 'https://xxx.aws.supertokens.io/recipe/dashboard/user' \
--header 'rid: dashboard' \
--header 'api-key: <YOUR-API-KEY>' \
--header 'Content-Type: application/json' \
--data-raw '{"email": "<YOUR_EMAIL>","password": "<YOUR_PASSWORD>"}'

My email ends in

.dev

is there some validation going on?

Hi, I’m using Mailjet as a mail platform and would like to send supertokens mails using the service. In the SMTP docs, I can only finds fields for providing a username / password. However, Mailjet only provides me with an API key and secret for the SMTP instead of credentials. Is there a way to configure Mailjet for use with Supertokens anyway?

Hi, do you support managed solution implementation?

hey super tokeneans. I got these "supertokens_python.exceptions.GeneralError: No SuperTokens core available to query" issues after configuring super token with React and Django rest framework. can anyone help me

Hi! This might be a dumb question but I was implementing the User Metadata feature, and added some metadata for a user. I was expecting to see the result in the supertokens user_metadata table, but seems to be empty. What does that table do then?