How to store api token in headless cms if user wants to save authorization?

Question

Web development

I came across headless cms and did not understand how the authorization saving logic should work when the user does not want to constantly enter a password. As you know, in headless cms you are given an api token with which you can perform manipulations. I guess that storing a token in an api cookie is not the best idea, so I want to ask the experts: can you explain on your fingers how authorization is saved?

Answer 1

they store it in cookies, in local storage, write their bikes, everything already depends on the specific task and implementation.