Hey, we have a problem with the client react on web. for some reason sometimes the refresh api from the backend response is 502 in the network interface but in the backend we can see in the logs it returned 200. Was wondering what this 502 means maybe you know and could help us?

Hi. I have implemented custom UI but standard flow password reset solution. Everything seems to be working except for the last part, where I call function submitNewPassword({ formFields: [ { id: 'password', value: newPassword } ] }). it gives me this error "Error: No instance of EmailPassword found. Make sure to call the EmailPassword.init method." Can enyone help me with this issue?

How exactly does the doesSessionExist work?

Is there a way to remove the "Powered by supertokens" text from the bottom of the sign up / sign in forms?

Hi, I tried running supertokens (the binary) in aws lambda and it doesn't seem to work. What I did was I downloaded the supertokens-postgresql binary, dockerize it by copying the binary over to the docker image and installing it there. I tried to "docker ps" into it and ran "supertokens start" and it worked. However, when I deploy the image to AWS lambda it fails to run everytime. Hence, I set the erro flag in config.yaml to "null" so that the error would show in std-in, and what I found was always a java exception, something related to read-only file system. I suspect this is because aws lambda has the entire file system as read-only, except for /tmp. But Supertokens is trying to write to /usr/lib/supertoken/webserver-temp. Any idea about this? I essentially tried to run "supertokens start" when the lambda function is triggered but failed to do so.

Hi guys. I am reading the CDI doc in swagger and I am trying to implement the sign up from my nodejs server, but I don't know how to use end point. I see that is a POST method and the end point is /recipe/signup but what is the route base or how do I have to implement the endpoint?

Has anyone found that when they're logged in with super tokens and the backend is verifying their ID, that after they move off the frontend tab for a bit and come back, the userId is rendered as null on the backend? But then when the frontend is refreshed, the userId is correctly set again

What could be causing the login to post to "http://localhost:3000/api/auth/authorisationurl?thirdPartyId=undefined&redirectURIOnProviderDashboard=undefined " when clicking on login with google/github? Nothing has changed with the code for a long time but it has decided to stop working

Hey there, @rp_st I'm currently integrating social authentication (google) into my application via SuperTokens. I'm looking to retrieve additional user details such as first name, last name, and gender from the social authentication process. However, it seems that these details are not being populated in the user data. as these are basic user details that must provided by google or any other social auth. Could you please let me know if there's any extra configuration required in the SuperTokens config to fetch these details, or if it's outside the scope of SuperTokens?