Hello, I am trying to implement social login (google).... async function googleSignInClicked() { try { const authUrl = await getAuthorisationURLWithQueryParamsAndSetState({ thirdPartyId: "google", // This is where Google should redirect the user back after login or error. // This URL goes on the Google's dashboard as well. frontendRedirectURI: "http://localhost:8100/auth/callback/google", }); /* Example value of authUrl: https://accounts.google.com/o/oauth2/v2/auth/oauthchooseaccount?scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email&access_type=offline&include_granted_scopes=true&response_type=code&client_id=1060725074195-kmeum4crr01uirfl2op9kd5acmi9jutn.apps.googleusercontent.com&state=5a489996a28cafc83ddff&redirect_uri=https%3A%2F%2Fsupertokens.io%2Fdev%2Foauth%2Fredirect-to-app&flowName=GeneralOAuthFlow */ // we redirect the user to google for auth. window.location.assign(authUrl); } catch (err: any) { if (err.isSuperTokensGeneralError === true) { // this may be a custom error message sent from the API by you. window.alert(err.message); } else { window.alert("Oops! Something went wrong."); } } } return { state, signUpClicked, signInClicked, googleSignInClicked }; }, }); and I get this error TS2345: Argument of type '{ thirdPartyId: string; frontendRedirectURI: string; }' is not assignable to parameter of type '{ providerId: string; authorisationURL: string; userContext?: any; providerClientId?: string | undefined; options?: RecipeFunctionOptions | undefined; }'.Object literal may only specify known properties, and 'thirdPartyId' does not exist in type '{ providerId: string; authorisationURL: string; userContext?: any; providerClientId?: string | undefined; options?: RecipeFunctionOptions | undefined; }'. What I am doing wrong ?

Hi, guys. Anyone has any experience adding Microsoft OAuth? Can you share some workarounds if there are needed please? Just starting out, trying to avoid common mistakes

Hello, I am facing blocking issue. I need to use the

exposeAccessTokenToFrontendInCookieBasedAuth: true

to verify a socket connection (as per https://supertokens.com/docs/session/common-customizations/sessions/with-websocket) I get an error that this option is not valid. I guessed it was because I was not using the latest version of the lib

supertokens-node

. Indeed I was using the

13.1.5

. Now that I updated to the

14

, it's working. But now I get an error

The running SuperTokens core version is not compatible with this NodeJS SDK

. I am using the

managed core

and I guess that the core was instantiated with a previous version. As I have no control on the core, how can I solve this?

Good morning! I have a question about session refresh and access token. We are seeing an issue that hasn't appeared before. And it happens when we change enviroment from localhost to a hosted backend cluster. For some reason i get the error "unauthorized" specifically when trying to call supertokens.attemptrefreshsession() in my react native client. But i'm able to get a user id from supertokens.getUser()

Hi guys! I've come across a pretty strange behavior. I'm using the SDK in a react native app. In order to maintain the session state i routinely check "SuperTokens.doesSessionExist()" and with that answer go forward with an authorized/unauthorized user. What i have discovered is that when the session expires, the method "doesSessionExist", still resolves true.

Hi, I followed the nestjs setup guide and when I went to auth/dashboard it showed a server error. Nest app shows this error: SuperTokens core threw an error for a GET request to path: '/apiversion' with status code: 401 and message: Invalid API key. The connection uri and api key in nest are the ones provided in the managed service, I don't know what could be wrong.

So I am using

FastAPI

and I would believe that the

Middleware

will add the

/auth

endpoints (set website_base_path) to the fastapi application, but it does not. I dont see any errors though. I tried the example from github, but no success ( https://github.com/supertokens/supertokens-python/blob/master/examples/with-fastapi/with-thirdpartyemailpassword/main.py )

how do i get getUserInfo to work

@rp_st need support, when we deploy Supertoken core to decrease access token validity from 30 days to one hour, we've got this error:

jwt invalid: failed to deserialize token claims: could not get token claims: go-jose/go-jose: unsupported key type/format

that's happen when and after we deploy it. Any reason why?

Hi Team, We are getting a KeyError 'access_token' on our Flask backend when fetching profile info via Google: supertokens_python/recipe/thirdparty/providers/google.py in get_profile_info at line 58 We think it is likely that the signup API is being called twice and returning a 500 response from Google the second time, which means that the auth_code_response does not have the 'access_token' key, and instead returns the following error: { error: 'invalid_grant', error_description: 'Bad Request' } We have looked at this thread https://discord.com/channels/603466164219281420/1113510798736752692 and its related GH issue (https://github.com/supertokens/supertokens-auth-react/issues/707) but haven't been able to come up with a solution. We also cannot reliably reproduce this error. Could we get some support / should the API be catching this to avoid the KeyError? Thank you in advance!