https://supertokens.com/
Join Discord
Which is the jwt token's key name in the cookie? `sAccessToken` or `st-access-token`. I think my oth...
# support-questions-legacy
a
Which is the jwt token's key name in the cookie? 
sAccessToken
or 
st-access-token
. I think my other environment is broken because of this. Both the node sdks are 
16.4.0
.
I'm manually verifying the JWT and I need the proper key name.
Looks like my other env is choosing header based auth automatically. I'll force it to use cookies.
After I explicitly set token transfer method in the backend and front end to cookie, I don't have any sAccessToken cookie anymore. 🧐
r
Setting it to cookie should create the sAccessToken, and for browsers, that is the default. How can we replicate this issue?
@aktopian seems like you are facing many unexpected issues. Could you upload an example app on GitHub that have all of these issues please?
Or give me access to your existing app? (I’ll be happy to sign an NDA if needed)
a
The token transfer method preferences are properly respected in my local node sdk, but not with the aws lambda, the front correctly sets st-auth-mode to "cookie" but the backend lambda is not doing it's job I guess. I've started clean slate a few times but still the same issue. Let me debug a little more and I'll get back. Thanks.
Found the cause I think, the response to my consume request doesn't have a set-cookie header, now I've to check if cloudfront, api-gateway removed it
r
Right. That’s probably the case.
a
It was cloudfront indeed 🙂
r
👍
PreviousNext
Powered by

SuperTokens.com

SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

Powered by