Hi. How can I catch errors in SuperTokens.init on the frontend. Assuming I get a 500 Internal Server Error because the supertokens core server cannot be reached

Hello, I have a doubt regarding multiple instances on the supertokens core running at the same time? I'm looking at the self-hosted version, and was wondering if I have 3 docker containers running the supertokens core and pointing to the same DB does this create an issue or can I have as many containers running as I need. This is for a High Availability simulations on my side. The full use case is for example putting all my core instances behind a load balancer so I don't have a single point of failure.

Has anyone used supertokens with Vue and SpringBoot?

ERROR [ExceptionsHandler] Received response with status 401 and body

Hi I'm using SuperTokens with NextJS. I am trying to protect a SSR page, so I implemented this code

const { session, hasToken, hasInvalidClaims } = await getSSRSession();

    if (!session) {
        if (!hasToken) {
            return redirect("/auth");
        }

        if (hasInvalidClaims) {
            return <SessionAuthForNextJS />;
        } else {
            return <TryRefreshComponent />;
        }
    }

But it redirect to /auth and therefore after I am back to the / page instead of the page from with I called redirect. How can I do so that it redirect to the previous page ? Thanks.

hey @rp_st i am getting a wierd behaviour, when i revoking all session for a user , authGuard is still able to allow the request.

I have a strange case where a request to the signout API returns a 401 in production. What’s the reason for that? How can I solve it? The issue is that users are basically never able to sign off

Hi could I get some assistance? I am working on a feature where I want to send a link as part of a confirmation email. I would like to create a magic link that authenticates a user and allows them to cancel a booking. I have been looking at this documentation https://supertokens.com/docs/thirdpartypasswordless/custom-ui/login-magic-link but I don’t necessarily want the email to be sent automatically as we have a trigger through Salesforce Marketing Cloud and I would to pass in a token as part of this magic link. But I am not sure how to proceed. Any advice would be appreciated.

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 ?

Is there a way to get localhost:3000/signup or localhost:3000/login in frontend, instead of just localhost:3000/auth?