Hello! I am trying to implement OTP in my Android app but the SuperTokens object isn't saving the session information. I am wondering if I initialized SuperTokens incorrectly (or something else) SuperTokens.Builder(applicationContext, apiDomain) .apiBasePath("/api/auth") .build() I can hit apiDomain on my local machine so we can assume this is correct I can see all the session data that I want in the response in logcat but I somehow can't access it in the SuperTokens object

Hello everyone, I'm new to SuperToken. I'm exploring whether that super token is a suitable solution for auth in our project. We are creating lot of white label applications under one login/signup process. every white label application has its own react native mobile application and nextjs web application. we also provide custom domain masking as well. We want login flow like : [username or email or mobile & password] or google/facebook Required signup flow: [email or mobile + otp] or google/facebook A problem is on the web we want to create sso.example.com for sharing one login/signup flow. is there any way I can share my session while redirecting to another domain(many cases not a subdomain) Thanks for even reading all these 😅 .

Hello, I'm getting a CORS Missing Allow Origin along with NS_ERROR_DOM_BAD_URI when calling the signin endpoint from my custom UI and can't figure out what I'm doing wrong (More details in the thread)

Is it safe to set checkDatabase to false in verifySession for all endpoint if I am writing my own logic for checking revoked blacklisted tokens? What does supertokens core check apart from checking whether the token is blacklisted?

hey @josephmilanmd our sdk does not return a 403 for this route. Maybe something else is doing that on your end?

Hi, I need your help, is there a way in supertoken for Google-One-Tap, for social login?

Is there an easy way to add claims (like the users email) to the session on the frontend? Asking because im following the flow for OIDC login with Okta with a custom built UI and we have to call signInAndUp() from the frontend like here https://supertokens.com/docs/thirdparty/custom-ui/thirdparty-login. We get the users email from the signInAndUp response but not sure where we can add it to the session from here. Unless maybe added a custom next api route to invoke the createNewSession function from supertokens-node?

How to override default styling that has !important on it in the prebuilt UI? The Google Icon has an extra margin left for some reason

And if possible to have a “drop in replacement using OAuth” for what we have today, is there an architecture where: The user hits login -> redirect to a service that’s using SuperTokens+Jackson under the hood, they login, we issue an Access Token, RT/Cookie, and issue it to my front end? And then on the backend I can point it at a JWKS for a token verification?

Hi.. we are using cookie based auth, class Onboarding(APIView): @method_decorator(verify_session()) def put(self,request,role): user_id = request.supertokens.get_user_id() print("User_id: ", user_id) It is giving error as "request doesn't have supertoken" I want to access session in class based sync function