Hi, I'm trying to implement supertokens into my nestjs + nextjs application with ThirdPartyEmailPassword. I encountered an error when trying to signin/signup with Google. The account is successfully signup/signin in the development environment but the /signinup api failed with status code 500 on frontend 400 on backend, then the error got displayed on the form. When reload the frontend application, it does recognize that I've logged in and redirect to the home page tho.

If the supetoken-core is running in docker, How to allow cors origin? I am getting this error - "from origin 'http://localhost:3001' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Credentials' header in the response is '' which must be 'true' when the request's credentials mode is 'include'."

Hi all, we put together some scripts to migrate users (along with userid mapping, roles and metadata) from one supertokens deployment to another. Hope it can be useful to some of you 🙂 https://github.com/Solgt/supertokens-migration

hey @rp_st i am getting a wierd behaviour, when i revoking all session for a user , authGuard is still able to allow the request.

Is there a way to auto set primary user on sign-up? Otherwise I override signInUp on backend and call createPrimaryUser

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.

Why session.getSessionDataFromDatabase returning and empty object ? Is it because there is nothing in the session data by default or what ?

I got 405 when signin/up. I am using NextJS and passwordless login. (Phone) I have

pages/api/auth/[[...path]].tsx

and it's content is same as doc. This is my appInfo

export const appInfo = {
  appName: NAME,
  apiDomain: DOMAIN,
  websiteDomain: DOMAIN,
  apiBasePath: "/api/auth",
  websiteBasePath: "/auth"
}

I can see UI in

<DOMAIN>/auth

, but when I provide phone number and click continue, I got this.

[Error] Failed to load resource: the server responded with a status of 405 (Method Not Allowed) (refresh, line 0) <DOMAIN>/api/auth/session/refresh

[Error] Failed to load resource: the server responded with a status of 405 (Method Not Allowed) (refresh, line 0)
<DOMAIN>/api/auth/session/refresh

[Error] Failed to load resource: the server responded with a status of 405 (Method Not Allowed) (refresh, line 0)
<DOMAIN>/api/auth/session/refresh

[Error] Failed to load resource: the server responded with a status of 405 (Method Not Allowed) (code, line 0)
<DOMAIN>/api/auth/signinup/code

I'm new to setting up oauth providers and such, and am currently getting back the no email given by provider error from my Azure AD integration. Are there any common gotchas that might cause this type of error? I'm sure it's something simple in my Azure AD app registration that I'm no doing right