"SESSION STORED IN A COOKIE" session is never stored in the cookie and there is more to tokens than JWT. The token can be an identifier that is saved in a cookie that matches the session on the server. So you can have all your cases as one case.
I did not say that "SESSION STORED IN A COOKIE" instead if you read well I said "Session data is stored on the server side, but a seession_id is stored on client side in a cookie. It allows the server to match a given user with the right session data""
"SESSION STORED IN A COOKIE" session is never stored in the cookie and there is more to tokens than JWT. The token can be an identifier that is saved in a cookie that matches the session on the server. So you can have all your cases as one case.
I did not say that "SESSION STORED IN A COOKIE" instead if you read well I said "Session data is stored on the server side, but a seession_id is stored on client side in a cookie. It allows the server to match a given user with the right session data""
Please read it again, this is the section title copy/paste from the article I didn't wrote this down:
SO YOU ARE PROBABLY WONDERING WHAT IS THE DIFFERENCE BETWEEN A TOKEN AND A SESSION STORED IN A COOKIE
ohhh sorry about that, updated. thx