Skip to main content

Authentication and Authorization for Backend Developers

Authentication and authorisation in a backend are two separate checks: authentication proves who the caller is, and authorisation decides what they may do. Common mechanisms are server-side sessions with cookies, JSON Web Tokens, and OAuth2 for delegated access, with models such as RBAC controlling permissions.

Stage: Security and Authentication · Part of the Backend Developer roadmap · Last reviewed 19 November 2026

What to learn in Authentication and Authorization

Authentication and Authorization interview questions

What is the difference between a session and a JWT?

A session stores state on the server and gives the client an opaque id in a cookie, so it can be revoked instantly. A JWT is a signed token holding claims that the server verifies without lookup, which scales easily but is harder to revoke before it expires.

Why should passwords never be stored with plain SHA-256 alone?

Fast hashes let attackers test billions of guesses per second after a leak. Password hashing functions like bcrypt, scrypt and Argon2 are deliberately slow, salted and tunable, which makes brute force far more expensive. Each password also gets a unique salt to defeat rainbow tables.

Where Authentication and Authorization fits in the Backend Developer roadmap

Authentication and Authorization belongs to the Security and Authentication stage (beginner level), which takes about 3 hours. Protect users, data and services.

Back to the full Backend Developer roadmap