Hi, I have a problem with signing up into my self-hosted backend. I was following instructions in https://supertokens.com/docs/emailpassword/quick-setup/backend. I am using Angular application, and I'm trying to integrate SuperTokens into my app. My backend is in the same project as the main app, could this be a problem? Thanks for help in advance!

Backend not working

Hi, I suspect that my docker image running the core is shutting down from time to time. I am hosting it on a digital ocean droplet. Do you have any ideas for why this might happen?

Core shutting down issue

Hiya! I was wondering if somebody has a usecase example for integrating supabase with supertokens, and not just using supabase auth?

Integrating with supabase

Hi, I'm trying to integrate SuperTokens into my Angular application, by following https://supertokens.com/docs/emailpassword/quick-setup/backend Adding frontend pre-built ui went smootly, however after adding these lines of code to main.ts into my app completely stops working, giving white page in browser and error in DevTools What do you mean in your guide by "Add the code below to your server's init file.", what file is it in angular app? Could you help me resolve this issue? Much thanks.

Angular + supertokens

Hi, Is there a way to get the user id from the request without calling the supertokens core (jn python)? Currently i do this:

python
session = await get_session(request, session_required=True)
user_id = session.user_id

Because i need the user id for every request, this havely slows down my api calls.

Hey guys! I'm pretty sure I'm doing something stupid here But I'm getting a 404 when frontend is trying to reach the auth endpoint http://localhost:3000/auth/authorisationurl?thirdPartyId=google I have configured apiBasePath as

/auth

Anything I can check?

(emailpassword & session - react - python-flask) email verification failing

I have an odd scenario: On local a successful signup will assign

sIRTFrontend

sFrontToken

sIdRefreshToken

and

sAccessToken

cookies and store them on the browser. On prod a successful signup will only assign

sIRTFrontend

and

sFrontToken

In both cases the user is added to the db under the correct (emailpassword) recipe. If I navigate to

/auth

on prod, I'm still redirected to

/

, so the

EmailPasswordAuth

component is still detecting some sort of logged in session but the cookies are not present or working in the browser cookies nor being transferred with the request credentials. This all works on local. I cannot for the life of me, figure out why the local implementation would be different?

hey guys

i was wondering if there was a way to add stuff to to a users details using django serializers and all

e.g when an uber ride is done, a command adds a value of 1 to the driver’s jobs_completed field

using django’s rest framework http requests serializers and all

User metadata

Hi, I can’t figure out why Supertokens.doesSessionExists returns false in my react-native implementation. What is the condition for it to be true ? Is there something I must save in my localStorage ?

more of a design question, but is there some standard way of making supertokens-react work with something like react-query? react-query provides a useQuery hook which fetches data from the backend on first render. however, if the session is still loading, this will fail, but returning null if the session is loading is not an option either, since react does not allow conditional hooks (returning before useQuery is not allowed).

useQuery with session loading

Hello, I want to setup Super Tokens Core on my machine for R&D purposes. I follow the step in the docs to setup without docker but I ended up with an error "ERR_CONNECTION_REFUSED" on Chrome, I setup mysql and I have 2 lines in the key_value table. But when I try with Docker I get the Hello from the /hello route. Any ideas ? I tested with WSL2

Connection refused error

Hi, I am wondering if it is possible to programatically create magic urls and send them out via SMS instead of requiring the user to input the number first?

magic link customisation

Hey, I realized the auth cookie isn't sent on mobile browser (tested on ios Chrome & Safari) so I get

refreshSession: UNAUTHORISED because idRefreshToken from cookies is undefined

is there any workaround? i'm working on a responsive PWA with nestjs + graphql + React

How do the

supertokens-node

verifySession

and

Session.getSession

functions behave in case the session is expired? Do they check this? or will they return `null`/`undefined` in such an scenario?

Hello, I am running a setup of nest.js and hasura with supertokens thirdparty-email and sessions, my frontend is react native and we do GraphQL queries to the hasura API with Apollo except for our login that’s just a rest endpoint in our nest.js backend where we use axios. The security is setup so that hasura receives the requests and then it forwards the headers to our who-am-i endpoint that in turn extract the userID from the session with your SessionContainer class after which it refactors the headers into a format that hasura can understand and responds back to hasura with that, hasura in turn uses that for it’s query that then gets sent back to the frontend. 

 All of this has been working as expected in our local development environment, but once we started hosting it things went wrong. I’ve console.logged inside of the login method in the nest.js backend to see that a correct session is returned, which it is, and we’ve used the react-native SDK to see that a session is created which it is as well as console.log() on our app context to see that the session is there as expected. But none the less no headers gets attached to our Apollo requests, does anyone have any idea what could be causing this?

 P.S I’ve also checked the instance of supertokens-core and everything seems to be working as expected there as well. What's really confusing me here is that the frontend seems to have all the data, both in the ctx and when doing checks with your SDK, but it none the less is not used in the apollo requests.

Hi, I have a question, why when I update user metadata by id and user with this id doesn't exist in database, this process create a table entry with this id and data? Can I fix it or check existance of user in easy way?

hi, i have a question. I'm implementing apple thirdparty signin. the flow works fine and apple call my api/auth/callback/apple with response status 200 but the backend don't return to my website domain. In Chrome console i have this error: "Refused to execute inline script because it violates the following Content Security Policy directive: “script-src ‘self’“. Either the ‘unsafe-inline’ keyword, a hash (‘sha256-O+xgXnYzZer/Ev6f0GV4Y96/B1k6naW0deebXvwnaXQ=’), or a nonce (‘nonce-...’) is required to enable inline execution." Can u help me?