Can you specify cookies for cookie storage?

[jrp-23]

I’m considering using cookie storage for the purpose of sending a JWT to the server on every HTTP request.

I configured my app to use cookie storage but doing so will include all 3 JWTs (id, access, and refresh) as separate cookies. All 3 cookies will be sent for each request, but I only need 1 (access token). I don’t want the other 2 cookies sent as it is unnecessary additional payload which has the potential to decrease performance.

My question is: can I specify that just the access token is stored in a cookie?

[powerful23]

@jrp-23 sorry but for now there is no way to do that. Will mark as feature request.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[scorgn]

We are having issues with our websites as the header size is too large with all of the cookies that are set. We also only need the access token. This feature would be nice. As of right now we're looking at having Amplify use local storage and additionally setting an access token cookie, but that's messy.

[pwfcurry]

You can use a custom storage & filter out cookie keys you don't want to use.

https://aws-amplify.github.io/docs/js/authentication#managing-security-tokens

Related: #1545

[ericclemmons]

Closing as https://docs.amplify.aws/lib/auth/manageusers/q/platform/js#managing-security-tokens is the best way to customize credential storage.

It's worth noting that 431 errors can occur for tokens with a large number of claims!

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.