Objective –
- meaning /structure of security mechanism
- where used? use case
- Implementation
Index
- Introduction
- Basic username-pwd
- JWT
- Oauth ( micro-services)
- Digital Signature (NPCI)
Introduction
Session, Cookie, JWT, Token, SSO, and OAuth 2.0 – here’s what you need to know
These terms are essential for identifying, authenticating, and authorizing users online. Let’s dive in๐
๐ช๐ช๐ช-๐๐๐๐ต๐ฒ๐ป๐๐ถ๐ฐ๐ฎ๐๐ฒ
๐น Oldest & most basic method
๐น Browser asks for username & password
๐น Lacks control over login life cycle
๐น Rarely used today
๐ฆ๐ฒ๐๐๐ถ๐ผ๐ป-๐๐ผ๐ผ๐ธ๐ถ๐ฒ
๐น Server maintains session storage
๐น Browser keeps session ID
๐น Works mainly with browsers, not mobile app friendly
๐ง๐ผ๐ธ๐ฒ๐ป
๐น Compatible with mobile apps
๐น Client sends token to server for validation
๐๐ช๐ง (๐๐ฆ๐ข๐ก ๐ช๐ฒ๐ฏ ๐ง๐ผ๐ธ๐ฒ๐ป)
๐น Standard representation of tokens
๐น Digitally signed & verifiable
๐น No need to save session info server-side
๐ฆ๐ฆ๐ข (๐ฆ๐ถ๐ป๐ด๐น๐ฒ ๐ฆ๐ถ๐ด๐ป-๐ข๐ป) & ๐ข๐๐๐๐ต ๐ฎ.๐ฌ
๐น SSO: Log in once, access multiple sites
๐น Uses CAS (central authentication service)
๐น OAuth 2.0: Authorize one site to access info on another
Techglot 