Great 😄 Any benefits to implementing the

sendEmail

override in addition?

What emails are sent if type is not PASSWORDLESS_LOGIN?

You can hover on the type and it should tell you.

ah gotcha! haha good 🤦‍♂️

Hello, i need to configure the backend for to accept capcitor://app.id URL and not only http or https. Someone can help me?

It would be a good idea to document the email verification case. The interface of

input

is different from the passwordless login case, and also different from the other email verification sending function. As far as I can tell, the link is in

input.emailVerifyLink

and the email is in

input.user.email

How come the input.email is undefined when I'm signing in with an email?

Hi, I am try to use useSessionContext to get user info in frontend. After I wrap _app with the error shown. What should I do ?

Is there no way to rotate the core api key?

Rotate core API key

Is there an easy way to share a session on 2 localhost frontends on 2 different ports? e.g. localhost:8080 and localhost: 9000

Is there any limitations to just insert users into the supertokens tables?

is there a changelog somewhere for specific releases? curious what's on v10

Hey @ZeferiniX yea. The node repo has a Changelog.md file. But in short, we added a new feature that enables you to send a new type of reply from the backend to display custom error messages in the frontend UI. This was a breaking change from an API interface point of view. Hence a major version upgrade.

Does it break anything when only using session recipe on v9? also does core need an update as well?

You will need to also upgrade the frontend SDK to the latest one. And that’s all. No affect on the core, or anything else.

aight, thanks and keep being awesome!

how do i start the core?

We are having an issue with our hosted api on vercel (nextjs)... The cookies are not set when requesting from a different origin (for example: capacitor://localhost)

I am migrating users, and I have a problem with some characters in the metadata. Characters like "ä" are "ä" in the database. I am using the supertokens Metadata recipe to insert the metadata. What charsets and collations does Supertokens expect? Is there anything I can do?

Hello everyone, I'm redesigning authentication pages, and have chosen to use

APIs

with

Axios

directly to authenticate users, I'm having issue with

thirdParty

implementation. the

state

query is missing in my callback page after using axios with url :

...../auth/authorisationurl?thirdPartyId=github

and

GET

method will always redirect to default callback page then it ends by redirection to

signin?error=signin

Hi, We are having trouble with requesting our backend from different origin(s). Due to

sameSite: lax

the tokens are not passed to the request and therefore all requests to our supertokens backend are unauthorized.

supertokens.init({
    ...frontendConfig().appInfo,
    cookieHandler: capacitorCookieHandler,
  })

The cookies are saved in localStorage. Do we need to create our own interceptor to add the cookies to the request headers?

Hey, I'm having some problems upgrading my supertokens-node backend to the latest version.

I think I've eliminated all of my technical debt, but now I'm getting a 500 on the frontend when trying toPOST to /auth/session/refresh

any documentataion regarding how to create user

for fastify

Sometimes get this error when testing locally.

Access to fetch at 'https://staging-auth.domain.com/auth/session/refresh' from origin 'http://staging-beta.domain.com:9000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header has a value 'https://staging-app.domain.com' that is not equal to the supplied origin. Have the server send the header with a valid value, or, if an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

staging-beta

is local with custom homain in hosts.

staging-app

is in the cloud and thats where the user logins. Usually happens when I close the browser and then open it directly on

staging-beta

locally.

hey I implemented my project with supertokens and wanted to automate the backend site with a docker compose file. Everything works fine but the signup and signin routes are not. Any Ideas? I can provide logs

It is possible redirect user to sign in and sign out page respectively?

Redirecting user