Depends!
With cookies, you don’t have to worry about sending the token to each request, as the browser takes care of this and other things like:
- send the cookie only to the domain in which it was allowed;
- control of the expiration time;
- you may have different cookies sent by
path
, within the same domain;
Cookie has size limitations (4 KB) when compared to localStorage (5MB), but to store tokens this will not be a problem.
But if you are working with Oauth, for example, which will commonly require you to control two tokens (the authorization token and the renewal token) and the advantages of the Cookie are not relevant in your context, it is best to focus both on the Store locale, for the sake of organisation.
This would be my position thinking about implementation. There are security issues of each solution which should be taken into account as well, as both solutions are vulnerable to some types of attack (XSRF, XSF and XSS).
Related: Differences between localStorage Vs sessionStorage?
– Renan Gomes