@User BE ---

SuperTokens.init({
    supertokens: {
        connectionURI: process.env.SUPERTOKENS_URI, 
        apiKey:process.env.SUPERTOKENS_API_KEY,
    },
    appInfo: {
        appName: "demo",
        apiDomain,
        apiBasePath,
        websiteDomain
    },
    recipeList: [
        Session.init({
            faunadbSecret: process.env.FAUNADB_SECRET_KEY,
            userCollectionName: "User",
            accessFaunadbTokenFromFrontend: true
        })
    ]
});

FE --- `const websitePort = process.env.APP_PORT || 3000; const websiteUrl = process.env.NEXT_PUBLIC_APP_URL || `http://localhost:${websitePort}`; if (typeof window !== 'undefined') { SuperTokens.init({ appInfo: { appName: "demo", apiDomain: websiteUrl, websiteDomain: websiteUrl, apiBasePath: "api/auth" }, recipeList: [ Session.init({ sessionScope: 'localhost' }), ] }); }`

Are the values of websiteDomain and apiDomain correct?

And please also make sure the apiBasePath is correctly set on the backend

Assuming the values above are correct, can you please send a pic of the cookies section set on ur browser after login?

Are u using axios on there front end?

nope

Is there anyway to check if there are interceptors to fetch being added?

Cause it seems like the interceptors are not being added.

The interceptors add some tokens on the front end which are all missing.

And the interceptors get added when you call the init function on the frontend

So first you should make sure that the init function on the front end is being called

@User , to check if the

fetch

interceptors have been added successfully, please open your website on google chrome, go to console, and type

fetch

. If you see the following output (see image in this message), that means the interceptor has been added successfully. If you see something else, then the interceptors were not added, and that's why the various tokens are not being set on the frontend. Please let me know what you see. Thanks

Hi, how can we pass the username password in the url for logging into the supertoken account?

I'm not sure I understand your question. We offer email / password login at the moment and neither of them are passed in the URL for security reasons...

Thanks RP

🙂

@User one more reason why you might be facing the issue, even if the interceptors are being added is cause you may be creating a session as a response to a browser level navigation. This means that the interceptors cannot handle the response to add some of the relevant tokens. If this is the case, you want to make sure to create a session only as a response to an API call from your JS code that runs on the frontend.

Thanks @User creating the session only as a response to an API call fixed the issue.

👍

Hi everyone! Can I ask how you achieve bundling the JDK with your releases? Is it something a layman programmer can do? 🙂

Hey!

So we have two forms of distribution - with and without docket#r

Docker *

For the one without docked, we provide a zip file that contains the JRE (subset of the JDK). The executable writhing the zip file refers to the Java executable inside the JRE folder to run the JAR files

The docker images works in a similar way

So a release is essentially a zip folder containing a few jar files, the JRE and an executable script.

@rp - thanks for your answer, so do I understand it correctly if you for example just need javac - can I just take that executable and then distribute it? (I'll probably need some sources as well I guess?)

You don’t need to distribute javac. You use that to create the JARs which are distributed along with the JRE

Ah I see. Thanks! I need to dig a little more. Thanks again for your time!

👍hope I helped.