I'm trying to get user name and surname following this section of the guide https://supertokens.com/docs/thirdparty/common-customizations/get-user-info where I should be able to access data with

override: {
                functions: (originalImplementation) => {
                    return {
                        ...originalImplementation,
                        // override the thirdparty sign in / up API
                        signInUp: async function(input) {
                            // TODO: Some pre sign in / up logic

                            let response = await originalImplementation.signInUp(input);

                            if (response.status === "OK") {
                                // This is the response from the OAuth tokens provided by the third party provider
                                let accessToken = response.oAuthTokens["access_token"];
                                // other tokens like the refresh_token or id_token are also 
                                // available in the oAuthTokens object.

                                // This gives the user's info as returned by the provider's user profile endpoint.
                                let firstName = response.rawUserInfoFromProvider.fromUserInfoAPI!["first_name"];

                                // This gives the user's info from the returned ID token 
                                // if the provider gave us an ID token
                                let lastName = response.rawUserInfoFromProvider.fromUserInfoAPI!["last_name"];
                            }

                            return response;
                        }
                    }
                }
            }

in the ThirdPartyEmailPassword.init() function in config.ts provided by the pre build code. Once here, what am I supposed to do to get name and surname? store it in metadata and then retrieve them through an api call?

Hello, I'm trying to authorize with Twitter Oauth2, her's my custom provider config:

{
          config: {
              thirdPartyId: "twitter",
              name: "Twitter",
              clients: [{
                  clientId: twitterClientId,
                  clientSecret: twitterClientSecret,
                  scope: ["users.read"]
              }],
              authorizationEndpoint: "https://twitter.com/i/oauth2/authorize",
              tokenEndpoint: "https://api.twitter.com/2/oauth2/token",
              UserInfoEndpoint: "https://api.twitter.com/2/users",
          }
        }

I'm using core5 and the follow version of the npm packages: frontend: "supertokens-auth-react": "0.31.0", "supertokens-web-js": "0.5.0", backend: "supertokens-node": "^13.6.0",

Has anyone had this problem? It happens constantly, but the user just needs to try to login/request again and it works.

Hello, i need to configure the backend for to accept capcitor://app.id URL and not only http or https. Someone can help me?

SESSION STILL AVAILABLE AFTER REVOKING IT

Hello 🙂 Im trying to self host supertokens-core with google cloud run but the database still in memory even with external connection credentials given. Can anybody help me?

Hi 👋 . I'm setting up supertokens with Next.js for the first time and have a basic question. In SSR setup (https://supertokens.com/docs/thirdparty/nextjs/session-verification/in-ssr), the "needs-refresh" prop is added so that would "force the frontend to try and refresh". Is there a way for this to be done on the server? If done on the FE, I think that means SSR isn't really working as it should.

Hello, Sometimes i am getting the error

supertokens_python.exceptions.GeneralError: No SuperTokens core available to query

. Is this caused by network issues? (i am using the managed service)

Hi, is supertokens HIPPA compliant? We are looking at several companies and Auth0 i/ Microsoft are the only ones that seem to provide a Business Associate Agreement and PCI compliant environments.

I have an issue with refreshing tokens with Next'js & Nest.js. I have followed guide for Sessions with Server Components: https://supertokens.com/docs/thirdparty/nextjs/app-directory/protecting-route#sessions-with-server-components--pre Everything works fine until the access token expires and new one has to be issued. Then at this moment I receive an error that prevents anything from rendering.

Warning: Functions are not valid as a React child

Refreshing the page afterwards with a valid access token doesn't cause issue. This stacktrace also mentions

SessionAuth

component, which makes me suspect that it's problem with the SuperTokens itself. Let me write this step by step what happens: 1. Refresh token epxires. 2. Browser sends two requests to:

/auth/session/refresh

and then

/auth/session/verify

(but not always). Response status codes are

200

3. While these requests happen, nothing is being rendered. These requests set the cookies accordingly. Error pasted below. 4. Refreshing site once again makes everyghing "just appear" and application behaves as desired. I have tried lowering the time

ACCESS_TOKEN_VALIDITY

environment variable to a few seconds to make sure that it's the invalid access token that causes trouble.