Hey guys, what could be causing this infinite refresh? Is there any information I can provide

Hi, when i use supertokens as microservice with nginx, for requests i get 'Cannot send secure cookie over unencrypted connection'. So, other services, like strapi, have a specific config settings to avoid this. Are any in supertokens to fix this?

Hey guys, I'm trying to implement PhoneNumber-Password recipe in Python Django framework and I'm stuck with overriding the reset password logic

Hi! I'm trying to implement SuperTokens social + email/pass together with Hasura actions, nest.js backend and a react-native front end. I've come across a problem that i don't really understand. I have a functional action in hasura, that for all i know, runs the function in the nest backend and returns a successful login from Supertokens. But for some reason, the session is undefined in the react native client. Does this ring any bells for anyone? I'm not getting any errors or trace stacks, that's what makes this hard. I just want to understand why my sessions is not set. /all the best, Farmo-dev

Hi, is there any option/function in thirdparty/emailpassword/passwordless to send email after sucessfull registration?

is there a way to list all users?

which users?

List all users

Hello , I am using the thirdpartypasswordless recipe for backend and hosted the supertokens core using helm-chart with following config snippet [ref : https://github.com/supertokens/supertokens-docker-postgresql/tree/master/helm-chart ] __________________________ # -- Time in seconds for how long an access token is valid for accessTokenValidity: 604800 # -- If true, allows for immediate revocation of any access token. Keep in mind that setting this to true will result in a db query for each API call that requires authentication. accessTokenBlacklisting: false # -- If this is set to true, the JWT (access token) signing key will change every fixed interval of time. accessTokenSigningKeyDynamic: true # -- Time in hours for how frequently the JWT (access token) signing key will change. This value only makes sense if "accessTokenSigningKeyDynamic" is true. accessTokenSigningKeyUpdateInterval: 168 # -- Time in mins for how long a refresh token is valid for. refreshTokenValidity: 1209600 # -- Time in milli-seconds for how long a password reset token is valid for. passwordResetTokenLifetime: 3600000 ______________________________________ Now, on successful signin, the session is created but its expiry is way too long (~2 years) in the DB row of session_info table against the corresponding session handle, however, I have intended to set the expiry to 604800 seconds (7 seconds) as mentioned in the helm-chart values note that on decoding the sAccessToken on online jwt decoder for the same session handle, it gives the expiry timestamp of 7 days from creation however in code, this statement: expiryTimestamp, err := sessionContainer.GetExpiry() is returning the expiry timestamp of about 2 years from now, which is same as the DB entry in session_info table

Sess

Hi, I'm thinking about switching my server environment to functions / edge functions. There's seemingly support for functions but your docs state:

Please refer the Serverless Deployment section (Towards the bottom of the navigation index)

Which I can't find, does it exist or am I blind? 😅 Regarding edge functions environment, I'd like to use Cloudflare Workers, do you offer native support for the runtime?

To handle actions after the signup at https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/handling-signinup-success with

override_thirdpartyemailpassword_apis()

is it possible to get the user id? I would expect that

client_id

will have one, but it is

None

.

Hello, i have a little problem with cors policy settings. Everytime i login in, i get errors below. Backend is written with expressjs, front end with react.

Hi, is there a way to setup a predefined test phone number and sms code for passwordless auth in supertokens-node? e.g for phone number 12345678 and code 123456 bypass sms auth and create session for a test user?

Hi, I'm trying to implement a basic POC in python (running core in a docker container), but I'm having issues configuring supertokens. I'm just running a simple FastAPI server and want to test social login. However, I'm getting a bunch of log messages from the middleware about not being able to handle my request (no recipe matched), and it looks like the middleware is just being bypassed. Here's my code (using the client_id/secret from the docs...)

I've implemented the with_thirdpartyemailpassword-2fa-passwordless 2FA example into my frontend template and all appears to be working fine excepts when I call

await signOut();

the client session hangs and becomes unresponsive and eventually chrome closes the window. There are no console logs. The functions makes a call to

http://localhost:3001/auth/signout

which responds 200 ... I was under the impression that a successful signOut yields 401. Does anyone have any suggestions? Is it okay to just post http://localhost:3001/auth/signout and then clear cookies?

supertokens-auth-react

self hosted core.

Hello, I've implemented emailpassword recipe with fastify node.js backend and vue 3 frontend. I did the rest api endpoints authentication using verifySession as per the documentation. But whenever the access token expires it doesnt get refreshed through refresh token and im getting an error message: "try refresh token". I dont understand where im going wrong.

message has been deleted

session refresh

hey guys

how can i get user info using a http request?

using django

and can i integrate the database with a rest api?

*database of users

@rp i mean using the fetch api to get user info and like maybe displaying it on a screen?

Hey there, it seems SuperTokens doesn't have a PHP SDK?

With PHP

Hi, is there any way to add own logger to supertokens to log requests (I am using middlleware)?

Hey, I'm looking at doing email verification but I store a username instead of an email. I bit of a complicated flow. We are wanting to be anonymous - hence the interesting use-case. But I want the flow to be: - Send verification to a specific email - User verifies the code within our app - User has a username automatically generated for them that we have stored in supertokens - User is able to then update their username / set a password if they chose (but we don't require them to)