Which is the jwt token's key name in the cookie? `...
# support-questions-legacya
aktopian
11/04/2023, 10:35 AMWhich is the jwt token's key name in the cookie?
sAccessTokenst-access-token16.4.0aktopian
11/04/2023, 10:55 AMI'm manually verifying the JWT and I need the proper key name.
aktopian
11/04/2023, 11:10 AMLooks like my other env is choosing header based auth automatically. I'll force it to use cookies.
aktopian
11/04/2023, 11:17 AMaktopian
11/04/2023, 11:43 AMAfter I explicitly set token transfer method in the backend and front end to cookie, I don't have any sAccessToken cookie anymore. 🧐
r
rp_st
11/04/2023, 12:01 PMSetting it to cookie should create the sAccessToken, and for browsers, that is the default. How can we replicate this issue?
rp_st
11/04/2023, 12:20 PM@aktopian seems like you are facing many unexpected issues. Could you upload an example app on GitHub that have all of these issues please?
rp_st
11/04/2023, 12:20 PMOr give me access to your existing app? (I’ll be happy to sign an NDA if needed)
a
aktopian
11/04/2023, 1:00 PMThe 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.
aktopian
11/04/2023, 1:09 PMFound 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
rp_st
11/04/2023, 1:12 PMRight. That’s probably the case.
a
aktopian
11/04/2023, 1:18 PMIt was cloudfront indeed 🙂
r
rp_st
11/04/2023, 1:19 PM👍