Dunicot’s Post

Understanding Session, Cookie, JWT, Token, SSO, and OAuth 2.0 Easily Explained in One Picture. When initiating a login session on a website, the management of your identity becomes pivotal. Here's an overview of how various solutions operate: Session: The server retains your identity information and issues a session ID cookie to the browser. This facilitates the server in tracking the login state. However, cookies may encounter limitations across different devices. Token: Your identity is encoded within a token dispatched to the browser. Subsequently, the browser forwards this token in subsequent requests for authentication. Notably, no server session storage is necessitated. Nevertheless, tokens necessitate encryption/decryption procedures. JWT: JSON Web Tokens standardize identity tokens by employing digital signatures to establish trust. The token encompasses the signature, thus obviating the need for server sessions. SSO: Single Sign-On leverages a central authentication service, enabling a unified login experience across multiple websites. OAuth2: This protocol enables restricted access to your data on one site by another site, all without divulging passwords. QR Code: Utilizes a random token encoded into a QR code for mobile login purposes. By scanning the code, users are seamlessly logged in without the need for manual password entry. The rise in QR code logins shows they are becoming more popular. Do you know how they work? #penetrationtesting #cybersecurity #websecurity #infosec

  • diagram

To view or add a comment, sign in

Explore topics