I discovered today that Playwright might give devs access to the browser's cookies. (Would have to confirm on my own.) If they do, it could be a great tool for testing example repositories since it also enables devs to disable JavaScript in the browser during end to end testing. If a set of standard test cases could be created, they could be run against any example repo to make sure everything still works as expected during repo NPM package upgrades, etc. Hoping to look into this sometime within the next 4 months. But sounds pretty exciting (since it would take away a lot of manual work).

why FetchError: request to https://....aws.supertokens.io/apiversion failed, reason: connect ETIMEDOUT 5

We are trying to host our system on GCP. We are using email password recipe and we want to use cloudrun. Just need some pointers on resources that will help to do this or if it is even possible. Thanks!

Hi, I'm looking for some clarification on the pricing change that seemed to happen March 18th. Is multi-factor authentication support via SMS something that we will be charged for even if we aren't using SuperToken's sending services? We're using our own service to send the text message after overriding the

smsDelivery

function, under the

Passwordless

recipe, and we were not expecting the new $100/month price minimum.

SESSION STILL AVAILABLE AFTER REVOKING IT

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?

Has anybody successfully set up SuperTokens for E2E testing with a Nest.js backend? I can't for the life of me get supertokens to initialize properly, or at all. I've followed the integration docs for Nest.js, and have set up a

SupertokensService

with a constructor that calls

supertokens.init({ ... config ... })

. This setup works great in both development and production. Among other things, we use

Session.getSession

during request processing. But for any request I send during an E2E test, I get an

Initialisation not done. Did you forget to call the SuperTokens.init function?

error. Also, the

/auth/signin

routes are not available. I've resorted to logging:

console.log('pre-init')
supertokens.init( ... )
console.log('post-init')

and sure enough, I can see my custom init logs, but still supertokens remains uninitialized. I've set

DEBUG=com.supertokens

, but this gives me nothing in the E2E test.

Did anyone set up Nuxt 3 + Supertokens? Any thoughts how to stay on SSR? Saw only NextJS in guides

Whats the difference between having

thirdpartyemailpassword

recipe compared to having both

emailpassword

+

thirdparty

recipes? I dont quite understand the

thirdparty

email part, isn't the email/ password auth handled by me? Specifically asking because Golang backend has both

emailpassword

and

thirdpartyemailpassword

recipes

/bin/sh: 1: java: not found

ubuntu how to install java and which version ? iam now working node test running but this problem cc: @rp_st