I have a strange case where a request to the signout API returns a 401 in production. What’s the reason for that? How can I solve it? The issue is that users are basically never able to sign off

We've noticed that some of our authentication-related emails are being flagged as spam by GMail (e.g. password reset). * We're using our own domain name * We're using Mailgun to send the messages * SPF and DKIM is set up correctly * The GMail message implies the risk factor is the content of the emails itself: "Similar messages were used to steal people's personal information. Avoid clicking links, downloading attachments or replying with personal information" Our next move, therefore, will be to change the content of the message so that it doesn't resemble the default ST template. Was wondering if other people had faced something similar and had success with a different approach?

Helllo, I tested my app locally and it works fine, but when testing in staging trying to signup/login I'm getting an error in the console saying: "SyntaxError: Unexpected end of JSON input". I checked the request and I get a 200 and I also checked the dashboard and the user was created.

Getting invalid api when curling to create a dashboard user with supertokens server -> curl --location --request POST 'Server link' \ --header 'rid: dashboard' \ --header 'api-key: ' \ --header 'Content-Type: application/json' \ --data-raw '{"email": "","password": ""}'

hello, im getting an error while creating roles. const response = await UserRoles.createNewRoleOrAddPermissions('free', [ 'read', ]);

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

Mkay. This kinda relates to the

Issue

I threw up on GitHub in

supertokens-node

. But this question is more specific. Is there an existing way to replicate the

/signin

,

/signup

,

/session/refresh

route middleware by hand? (And are those the only middlewares created from

app.use(middlewares())

?)

(Background in Thread)

Hi All, I have an Issue with supertokens-react-native. When using the signOut function, calling doesSessionExist still return true. Does anybody have the same issue ?

can any body tell me basic functions in supertokens for react and how to connect it with backend like a functional app authorization and authentication being given by supertokens learning from documentation is bit hard for me first timers

Hey guys. I had a question about the sendPasswordResetEmail method that we use to send a reset password link to the user. Can someone explain the different options available for how the email is sent? I checked the docs here https://supertokens.com/docs/web-js/modules/recipe_emailpassword.html#RecipeFunctionOptions but it isn't clear to me what the RecipeFunctionOptions object passed to recipe functions represents. Maybe an example of the options object and what it means can be helpful.