Here is my hook

ts
import { useQuery } from "react-query";
import { useAxios } from "./useAxios";

export const useGetPatients = () => {
  const { axios } = useAxios();
  return useQuery(["patients"], () =>
    axios.get("/patient", { withCredentials: true })
  );
};

You don't need to add any extra headers or anything for sessions to work

Nor do you need to set

{ withCredentials: true }

. It get's added automatically.

but adding that shouldn't make a diff

FE

ts
SuperTokens.init({
  appInfo: {
    appName: "tlantli",
    apiDomain: "http://localhost:5555",
    websiteDomain: "http://localhost:3000",
    apiBasePath: "/api/auth",
    websiteBasePath: "/auth",
  },
  recipeList: [EmailPassword.init(), Session.init()],
});

BE

ts
AuthModule.forRoot({
      connectionUri: 'https://try.supertokens.com',
      appInfo: {
        // Learn more about this on https://supertokens.com/docs/thirdpartyemailpassword/appinfo
        appName: 'tlantli',
        apiDomain: 'http://localhost:5555',
        websiteDomain: 'http://localhost:3000',
        apiBasePath: '/api/auth',
        websiteBasePath: '/auth',
      },
    }),

Seems about right!

When you sign in, what do the set-cookie headers look like?

hmmmmm, I restarted my FE and BE and it works now 😄

haha.. hmm.. strange

might have missed something? It's late here, maybe I'm going crazy

I have a react app + nest js backend and I did all of this in 30 minutes or so! Super awesome documents

that's a record!

awesome!

One question, when using third party provider authentication (google, fb, etc...) in conjunction with a self hosted approach, where does the data gets stored? all in my database?

I've never done social oauth

Yes. All in your db

What's the logic, when a facebook user changes email, from johndoe@gmail.com to johndoe2@gmail.com? There must be some internal UUID?

Yes. So fb issues their own user ID. We store that and that's the way we identify the same user. When someone changes their fb email, the change will be reflected in your db when then login again

Also, I noticed that you are using

EmailPassword

recipe, but have copied from the thirdpartyemailpassword docs? I would suggest that you always use

thirdpartyemailpassword

if seeing those docs.

oh yeah, missed that! you could tell by the comments on my code, right?

yes

Hello again, I have a problem with the Interceptors (401 Unauthorized), I think they don't work correctly for me. I am using NextJs and FastAPI. If I don't add { credentials: 'include' } it doesn't work either.

The

fetch

in

getServerSideProps

runs on the server. Therefore, that fetch doesn't have interceptors applied to it. If you want to get the session info in

getServerSideProps

, you can follow: https://supertokens.com/docs/thirdpartyemailpassword/nextjs/session-verification/in-ssr

umm Thank you so much

I am using the session recipe and have multiple api endpoints. I am using nodejs with express. https://supertokens.com/docs/session/common-customizations/sessions/session-verification-in-api/verify-session There is a code snippet to call verifySession let userId = req.session!.getUserId();

let userId = req.session!.getUserId();

is the not operator there returning false if there is a userId?

The “!” Operator is there to assert that req.session cannot be undefined

Cause from a typed point of view, req.session can be undefined if you pass sessionRequired: false when calling verifySession.