Hi, got a little issue with our Android app on react native for a few days. it can log in and get an access token but when refreshing it logs us out this is what we changed before it started to happen : - "supertokens-node": "^8.5.0", + "supertokens-node": "^9.2.3", in the same deployment, we also set the cookieDomain to a wildcard to allow subdomains the weird thing is ios is fine

Hi all I have a question Is super tokens support SSO(Single Sign On ) If i have multiple SPA frontend projects on different domains and i want to login once for all the fotnend projects Does super token support this functionality ?

Login to multiple domains via common auth

When migrating from auth0, why is it recommended to map the supertokens user id in my db? I ll use the exported json method and in the frontend I ll keep using the auth0 id. (for old users only) Also, when calling backend functions such as

getUserById

, siince I override them, I would anyway have to look in the json every time. Am I missing something?

Within the last day, Google Social Auth in our web app tries to log us in to supertokens.io instead of our app. We are providing the Google Clied Id and Secret associated with our app. We did switch from using an IP to our dev domain name in the last several days if that makes a difference. Why is it trying to log into supertokens.io?

Hello, I would like to be able to save additional user information during account creation using passwordless recipe. Can you tell me how I can get to this behavior?

Hello everyone! I have a general question about SuperTokens, I like the idea of using it as an authentication server for my fairly large architecture with multiple services, but I'll also need the flexibility which I'm not sure it has. I'm wondering if those will be easy features to add or not, so in your experience, is SuperTokens easy to integrate with? https://supertokens.com/docs/thirdpartyemailpassword/advanced-customizations/apis-override/usage One example I have is that I want to expose some LDAP functions using LDAP.js and allow access to SuperTokens users, I will also use the new UserRoles recipe to get the LDAP functionality SuperTokens provides: https://supertokens.com/docs/nodejs/modules/recipe_userroles.html Furthermore, it would be great, if I could have more direct control over SuperTokens, for instance I want to create a certain user type with preset fields if they're coming from a specific tool, which means I could either override SuperTokens hooks, or what I would prefer to do is call a custom API method like

POST /auth/<user-type>

and then call a function from SuperTokens SDK to create that user: https://supertokens.com/docs/nodejs/modules/recipe_thirdpartyemailpassword.html#emailPasswordSignUp-1 Is this a good way to go about it? Also, how much data is recommended to be stored with the UserMetadata recipe? Should it only be for very simple structs or can I use SuperTokens to handle business data such as a paid subscription or personal data? https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/usermetadata/about

Hi, We're authenticating our react app with supertokens react components successfully from SUBDOMAIN.DOMAIN.COM where our frontend lives and where the cookie is also set. Our main API and supertokens fastify middleware live on DOMAIN.COM/API and correctly set cookie and validate the requests The problem we have is that we have another authentication flow where customers will get a new supertokens cookie from DOMAIN.COM, they are supposed to be authenticated but the react auth component does not recognize it. Would you have a cue on how we could solve that?

Sharing session across sub domains

hey :). we are having an issue with the redirect uri returned for Apple on the web. the code that creates the redirect uri uses the API base path instead of the UI base path.

SuperTokens integration error in React JS project

I have another architectural question regarding SuperTokens and its Core. How suitable is the solution for use by multiple services? I would like to use SuperTokens to manage users which are authenticated into multiple apps, and plan on using the UserMetadata recipe as well as UserRoles recipe to store permissions, roles and groups (using the metadata as unfortunately groups aren't part of the UserRoles recipe). My question is particularly regarding some features like initializing recipes and creating all the roles and permissions - from what I can tell I just have to call an initialization method in my service and create all those beforehand to avoid issues later, but if I have to do this in every service just to ensure that the data really exists it seems like this isn't the best approach. How would you go about managing users that are accessed by different apps, and was SuperTokens built for this use-case?

By the way, when I run SuperTokens in Docker with the

--network="my-network"

flag, it seems that isn't respected and I just end up having to call

docker connect network my-network <container-id>

. Is this a known issue, or maybe I'm using the flag wrong? I tried changing the order. Of course I beforehand created the network with

docker network create my-network

.

for apple social login... i see the following in our Go service.

com.supertokens {t: "2022-07-11T22:32:26Z", message: "middleware: Started", file: "/go/pkg/mod/github.com/supertokens/supertokens-golang@v0.6.6/supertokens/main.go:31" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:32:26Z", message: "middleware: requestRID is: thirdpartyemailpassword", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:32:26Z", message: "middleware: Checking recipe ID for match: thirdpartyemailpassword", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:32:26Z", message: "middleware: Matched with recipe ID: thirdpartyemailpassword", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:32:26Z", message: "middleware: Request being handled by recipe. ID is: /authorisationurl", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:32:26Z", message: "Sending response to client with status code: 200", file: "/go/pkg/mod/github.com/supertokens/supertokens-golang@v0.6.6/recipe/thirdparty/api/authorisationUrl.go:46" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:32:26Z", message: "middleware: Ended", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} [GIN] 2022/07/11 - 22:32:26 | 200 | 484.992µs | 10.108.0.5 | GET "/auth/v1/authorisationurl?thirdPartyId=apple"

com.supertokens {t: "2022-07-11T22:33:00Z", message: "middleware: Started", file: "/go/pkg/mod/github.com/supertokens/supertokens-golang@v0.6.6/supertokens/main.go:31" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:33:00Z", message: "middleware: requestRID is: ", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:33:00Z", message: "middleware: Checking recipe ID for match: thirdpartyemailpassword", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:33:00Z", message: "middleware: Request being handled by recipe. ID is: /callback/apple", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:33:00Z", message: "middleware: Ended", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} [GIN] 2022/07/11 - 22:33:00 | 404 | 363.757µs | 10.108.0.5 | POST "/auth/v1/callback/apple"

com.supertokens {t: "2022-07-11T22:33:01Z", message: "middleware: Started", file: "/go/pkg/mod/github.com/supertokens/supertokens-golang@v0.6.6/supertokens/main.go:31" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:33:01Z", message: "middleware: requestRID is: thirdpartyemailpassword", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:33:01Z", message: "middleware: Checking recipe ID for match: thirdpartyemailpassword", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:33:01Z", message: "middleware: Matched with recipe ID: thirdpartyemailpassword", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:33:01Z", message: "middleware: Request being handled by recipe. ID is: /signinup", file: "/usr/local/go/src/net/http/server.go:2084" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:33:01Z", message: "errorHandler: Started", file: "/go/pkg/mod/github.com/supertokens/supertokens-golang@v0.6.6/supertokens/supertokens.go:227" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:33:01Z", message: "errorHandler: Sending 400 status code response", file: "/go/pkg/mod/github.com/supertokens/supertokens-golang@v0.6.6/supertokens/supertokens.go:227" sdkVer: "0.6.6"} com.supertokens {t: "2022-07-11T22:33:01Z", message: "Sending response to client with status code: 400", file: "/go/pkg/mod/github.com/supertokens/supertokens-golang@v0.6.6/supertokens/supertokens.go:286" sdkVer: "0.6.6"} [GIN] 2022/07/11 - 22:33:01 | 400 | 682.639µs | 10.108.0.5 | POST "/auth/v1/signinup"

after the 404 in the browser... i see a 200. the odd thing is the state query string value is empty. not sure if that is an issue or not. https://dev.wwwwww.us/callback/apple?state=&code=c209f066b40054a20944e1b21e6661f59.0.mruxx.e52D85TBP-Titom-vr8eDg

any help is much appreciated. i apologize for the spam

Sign in with apple in golang issue

Replied to you in a thread above

Hey guys, Are you planning to support passkeys in the future? https://developers.google.com/identity/fido

Hello everyone

I was wondering about

third party

and

email password

accounts linking issue, is there any news on how to map these two to same user, I mean is the issue out of the oven yet 😄

Account linking

Is there a way to store the user claim information from third party login in the session?

Is there a way to do single sign out from the Thriparty IDP, once the app is logged out using signout method?

hi can someone help me decrypt a hash using private rsa key?

Decryption

Using passwordless, is there a way to know if a user is new in the front-end? I am currently using the same page for login and registration.