How does CORS and JWT work in Laravel?

Question

JSON Web Token

There was already a similar one here, but no detailed answer was given. And my question is a bit off topic.
What interests me is this: when a user logs in, he is given a token, and where is it then stored? I mean, when I re-enter the site, I no longer require authorization, but there is nothing in the cookies. And why is an OPTIONS request sent every time? As I understand it, it is needed to get a token, but where does it get it from, where is the token stored?
I'm making an API and want to enable external resources (from other domains) to access it. But I ran into the question, how, after authorization, to get a token? The Authorization header appears only after a request of the OPTIONS type, it is not clear how and where the token is stored, how it is determined, because it always remains the same, is it stored somewhere in the cache?
I would be very grateful if someone could help me. I read the documentation, but as I already wrote, it is not clear in the end how to get the token of an already authorized user.

Answer 1

What interests me is this: when a user logs in, he is given a token, and where is it then stored?

on the client somewhere. The server should not worry about this, it does not store it. Well, that is, you received a JWT token, which means you need to check the signature. The signature is valid - the token is valid.
not authorization but authentication. Well, perhaps the token is transmitted in the headers (usually, anyway).
This is already related to CORS and is called freflight request. Before each request, your browser asks the server "what can I do with this url?". Well, the server returns based on your host, etc.
Typically, options requests do not require authentication. Well, at least in the ishus tracker for jwt, someone 100% asked questions about how to make friends with lib and cors.