but am not getting it anywhere

nor I can see in user details on supertokens user dashboard?

Hi, I already have a service that issues JWTs from different flows like Google, Apple, Verify Email, Email/pass. I would like to replace only the Identity verification part to start with and keep the user data etc in the existing application. Can I use Super Tokens to do this, i.e to have Super Tokens generate a JWT based on Goole, Apple, etc authentication flows (plus more) and then keep using the JWT in my front-end web and Apps?

Team, another quick question, how do I update user data in supertokens? like first name, last name, email verified etc?

Heyy Team.. I have setup supertokens core + DB on x.x.x.x What are the endpoints I can access so that I can sigin/up the user

Using only for session

Updating user data

Architecture question

hostname Error when running my server, client inside docker

this type true ?

new version 4.3 admin panel fixed login thank you

wow i liked. This api adress, pc, mobile etc Can it be added in additional specials such as

you can open an issue about this on our github, and we can work on that feature. But until then, you can add that info yourself in the session in the createNewSession override. But that info won't yet be displayed on the dashboard anyway.

this user delete but app refresh get see data

await Session.getAccessTokenPayloadSecurely()

User deletion but access token still works

supertokens + apollo graphql example used ?

With Apollo

capacitor with mobile app header dont add cookies, becasue diffrent url :/, how to fixed this app url

'capacitor://localhost',
    'ionic://localhost',
    'http://localhost',
    'capacitor://',

but api

api.xx.com

for some reason it doesn't add any cookies when leaving this backend ss

@productdevbook you may want to search discord for similar questions. This can come up in the past.

capacitor with mobile app header dont

@rp we are already solving this issue

Me and @nkshah2

If that’s finished he can just look at the example

can anybody tell me how can I trigger google auth directly (programatically) instead of clicking the button? Am using pre-built UI and for cordova I need to bypass the need to click the button again.

answer to question of why not open the auth url from cordova? why first open auth.example.com? coz I need to place some cookies first based on which token claims are set

My backend isn't based on Node, Go or Python, so I have the auth backend written separately in Node. The auth backend will be proxied based on the route. I'd like to secure my api backend apis, so I will call an api from my api backend to the auth backend, say

api/auth/verify-session

, and use

Session.getSession()

in the auth backend to verify the session. I'd like to know what all should be forwarded from the api backend to the auth backend, session cookie is one? Also is that data that should be forwarded subject to change? Am I using an internal implementation detail that can break?

I'd like to understand if it wasn't possible to just have the supertokens core and the backend available as a client lib for different languages that talked to supertokens core via http.

@rp can you please guide?

See the thread I had created @mib200

Facing issue connecting to an AWS RDS Mysql DB. Getting error: "What caused the crash: Failed to initialize pool: Index 1 out of bounds for length 1"