Hey! there is a blog post about how to setup social login with custom UI that might help: https://supertokens.com/blog/adding-social-login-to-your-website-with-supertokens We are also working on a non react SDK which will provide helper functions like

signIn

,

signUp

etc so that you don't have to make API calls manually.

@User so, I'm making a POST to

/auth/signin

with

rid: 'emailpassword'

header. I do get back a 200 with the json and the tokens in the set-cookie response headers. However, I'm a bit lost on what I should do after that. More specifically,

await SuperTokens.doesSessionExist()

returns false.

Have you called init on the supertokens-website repo? ANd on the backend, have you added session.init()? Perhaps you can share your frontend and backend config here.

@User Here you go. Context: I'm trying to use the JWT feature to integrate with Hasura. Frontend config:

js
SuperTokens.init({
  apiBasePath: '/api/auth',
  apiDomain: 'https://my.website.com'
});

Backend config:

js
supertokens.init({
  framework: 'fastify',
  supertokens: {
    connectionURI: process.env.SUPERTOKENS_URL,
    apiKey: process.env.SUPERTOKENS_API_KEY
  },
  appInfo: {
    appName: 'My Website',
    apiDomain: 'https://my.website.com',
    websiteDomain: 'https://my.website.com',
    apiGatewayPath: '/api'
  },
  recipeList: [
    EmailPassword.init(),
    Session.init({
      jwt: {
        enable: true
      }
    })
  ]
});

You need to set

apiBasePath

on the backend as well.

to

/api/auth

. And you can remove

apiGatewayPath

(unless you are using something like AWS's staging environment.

So, here's the situation, my backend is at

https://my.website.com/api

, which means that supertokens endpoints are at

https://my.website.com/api/auth

Yes. So you need to set

apiBasePath

on both frontend and backend to

/api/auth

And you can remove

apiGatewayPath

Then try again

@User the problem is that now my endpoints are at

https://my.website.com/api/api/auth

That's why I used

apiGatewayPath

.

I guess the frontend supertokens needs an

apiGatewayPath

as well, but I don't think that's an option.

That's odd. Using this on the backend config:

appInfo: {
    appName: 'My Website',
    apiDomain: 'https://my.website.com',
    websiteDomain: 'https://my.website.com',
    apiBasePath: '/api/auth',
  },

Will expose the APIs on

https://my.website.com/api/auth

@User Yes, but that assumes that the backend is running at root

ah i see.. okay. So the backend doesn't see

/api

part

Exactly.

it will only see

/auth

right

https://my.website.com/api

is an nginx reverse proxy.

So the config you set is correct indeed.

Can you show me the set-cookies headers from the sign up or sign in response?

@User where are we managing the users data ? i setup and using mongo as DB. I singed up couple of users but not able to see any users collection. There are only two collections : jwt_singing_keys and key_value

@User we don't support mongodb for login. By any chance, are you using the in memory db?

it is loading the storage layer and saying loading mongodb config

Got it. And when you call sign up, it doesn't throw an error?

No , I am able to login, signup , forgot password

huh. That's really strange. Not sure how that's possible

Unless the mongodb config is not set fully and it's still using the in memory db

What config have you set for mongodb?