Hi, in what ways we can prevent the accesstoken to be visible from the cookies on the frontend?

hey @vigneshkumar5238 you can't. Chrome shows it, and that you can't control

Integrating with hasura can actually prevent the original session details or hash to be not visible right? instead hasura claims will be visible if I'm right?

when you say visible, do you mean that the frontend JS has access to it? Or are you saying about visible to the user in the inspect element

I'm taking about the inspect element via the network or application tabs.

yea.. the cookies will be visible there always

My goal is that, my access tokens shouldn't be even in be accessed from cookies, since supertokens issue them in cookies right? Instead if I use Hasura or any other Integrations, supertoken's JWT won't be visible on the cookies right?

it will be. You can't prevent that

Okay, so what is the exact point of using the hasura integration with supertokens? https://supertokens.com/docs/passwordless/hasura-integration/without-jwt here it says, no tokens will be exposed to frontend. what does this mean?

it means that the JS on the frontend won't have access to the token. Which is different from the user being able to view the token