ok so im not that experienced in web stuff but does auth work like this?
go to auth page and send credentials
server checks credentials and issues a session token as cookie
client sends session cookie in header of every subsequent request
server uses session token for authorization and stuff
or is there a better way to do that
0 Boosts
0 Likes
@ramona@app.wafrn.net ohh nyaruhodo, thanks friendly entities
@majirubi@fedi.epicalert.xyz
always happy to help 😁
@majirubi@fedi.epicalert.xyz
yes, that's pretty much it
a relatively popular alternative is JSON Web Token, or similar mechanisms, where the token contains all the information needed (signed with a private key of the server, so the user cannot change it), and there is no session storage server-side, but that comes with another set of trade-offs (e.g. revocation of such tokens becomes complicated, in case of multiple servers the key has to be distributed to all of them, cookies have limited size, making the token also limited in size)