Different Web Authentication Flow [closed]

I read something a few months ago about an Authentication flow, where the server would validate the credentials and store something (token ? id ?) directly in the request’s headers.

The client would then just do normal requests without specifying any header and the token/id/hash would already be in the header for the server to validate (or it might already be validated).

Of course, I forgot about it for a while and now that I want to learn more I can’t find anything about it.

I’ve been crawling the OAuth website and other available documentations but can’t seem to find this one…

I don’t think it’s the Session Token Flow or other Authorization Code Flow but again, I’m not sure of what I read.

Does it ring a bell to you or did I invent this memory of mine ?

Thank you !