Last question for today 😅, how can I configure my SMTP with username/password credentials ? I can't find a way to give the username

I noticed that the Auth0 external id (

sub

) for the google provider was

google-oauth2|<ID>

. Now with supertokens I am building this within

createNewSession

, for mapping the accounts.

const externalUserId = user.thirdParty ? `${user.thirdParty.id}|${user.thirdParty.userId}` : null;

I noticed that

user.thirdParty.id

, here is

google

and not

google-oauth2

. Is it safe for me to simply replace the

google|

part with

google-oauth2

, is the

<ID>

part of the auth0 sub stable?

Can a SuperToken dev take a look at this and let me know which is the best way to "connect provider" with XenForo and SuperTokens https://xenforo.com/community/resources/th-connected-account-providers.8488/

It looks like SuperToken cookies are exceeding the permitted limit. I'm getting this error: "Set-Cookie header is ignored in response from url: http://localhost:4000/auth/session/refresh. The combined size of the name and value must be less than or equal to 4096 characters."

hi! how can i prevent

SignInUp

component from

supertokens-auth-react/recipe/passwordless

redirecting to

/auth

i am overriding it to only confirm

OTP

by creating

verify-phone

route, and adding this to frontend config

signInUpFeature: { disableDefaultUI: true }

hi, for our app we had to use the native http plugin from capacitor, which doesnt support interceptor... any example how to write custom logic to attach the cookies in the headers (for every request)?

Is there any chance a function could be added that returns the session found on the server instead of (or in addition to) adding it to the

request

object? (Talking about

Node.js

here.) I'm playing around with

Svelte Kit

. And it seems like they don't give us access to any data tacked onto the request object. I'm trying to figure out if there's a more functional way to get the session instead. 🤔

why FetchError: request to https://....aws.supertokens.io/apiversion failed, reason: connect ETIMEDOUT 5

Hi, has anyone tried using SuperTokens with HTMX? If so, do you have any guidance or advice?

Hi there! I'm planning to launch my app before the end of the month and I'm trying to implement a referral system, where new users can sign up only with an invitation code. My app is using the ThirdPartyPasswordless recipe, and contrary to the EmailPassword recipe, there's no Sign Up flow on which I can add another required field when signing up. As of now, I'm creating manually new users for my beta testers, and I'm denying signup if I can't find any matching email/phone in a

createCodePOST

API function override. I was thinking about exposing a route on my application to validate an invite code, in which the route would create a new user on Supertokens, hence enabling this email to sign in. However, in that setup, there's no way to verify the provided email authenticity, except if I implement email validation on my own, which isn't something I want to do. Can you think of other ways to implement that? Is that something that could be integrated within my Supertokens setup or should I think about this being outside of Supertokens' scope? I understand this is a kind of specific use case, and might not even be related to Supertokens, but still I'd love to hear your input on this 🙂