Hi please here me here how to setup the supertokens. I am using nest I have 2 microservice: M1 and M2 as API gateway. I have setup the supertokens in M1. it takes cred from M2 and signIn. and return Jwt tokens. In M2(no st) when i verify this token in M2 it gives : { "message": "Invalid token", "error": "Unauthorized", "statusCode": 401 }

hey @satty_71243 what token are you sending m2? And how are you verifying that token in m2?

i am creating the jwt token with payload of userId in M1 and sending it to M2 and varifying it in M2 using the method provided for microservices.

right. What does the jwks endpoint return if you go to that in your browser? Also, how are you creating the jwt?

using this method to create the jwt.

Yes

this endpoint kept loading in the browser.

Hmm. Then something is wrong

this M1 is on localhost:4001 & M2 is on localhost:4000

Can you enable backend debug logs for supertokens backend SDK and show the output when you call the jwks endpoint?

not getting anything.

That’s means that api request is not hitting your backend.

what could be the cause ? since my M2 is exposed to endpoints sends the "signing" event and M1 takes the events and using signin method from email and password recipe.

im really not sure what you have setup here.

let me know this flow if this is possible ? flow is like this, - user enters the credentials to M2 (no st init), - then M2 pass his cred to M1 (st init) and and it - authenticate the creds and generate jwt token as response. - then using this token in M2 for others endpoints.

yea, this is possible

after generating the token when verifying in the M2 it shows the un authorised

how are you trying to verify the token?

also dashboard is not accessible . using localhost:4001

it';s on localhost:4001/auth/dashboard

let me know if this is causing issue , M2 is communicating with m1 using TCP

Otherwise it will be hard to help out for free like this

sorry i am using this localhost:4001/auth/dashboard to access this but stuck on the loading

please providde console logs, network screenshot, backend error stack if any, version of the backend sdk, framework being used.

no i have setup all this from the docs. it is working fine when i remove microservice setup from M1 and login from endpoint auth/signin and generate token and verifying this in M2. in this approach M1 is exposed.