mufassall

Security / 1 / 3

Authentication

How a service learns who is calling: storing passwords so a leak is not a disaster, sessions and tokens, how long a token lives and how to kill it, logging in through an identity provider, and a second factor.

  • 14 min
  • Intermediate
  • 11 steps
Leaked hashes cracked
62 %
Login time
40 ms
Account takeovers
35 /day
Open in Lab
  • request
  • reply
  • redelivery
  • duplicate
  • lost

Numbers are a model scenario, not measurements

The real request

Attacker → Users DB

Request

SELECT id, email, password_sha256 FROM users;1

Response

120000 rows, first one:
{
  "id": "u_42",
  "email": "ali@example.com",
  "password_sha256": hidden,
  "salt": 2null
}
  1. password_sha256 · hidden — A fast hash of the password. Hidden here; in the leak it is a ready target for guessing.
  2. salt — None. Equal passwords give equal hashes, so one guess cracks everyone who chose 123456.
Course: 42 lessons
  1. 01 Foundations

    1. The life of a request
    2. Latency and throughput
    3. Napkin math
  2. 02 Scaling

    1. Scaling up vs scaling out
    2. Load balancing
    3. Stateless servers
    4. Caching
    5. CDN and edge caching
  3. 03 Data & storage

    1. SQL and NoSQL
    2. Database indexes
    3. Storage engines: B-tree and LSM
    4. Database replication
    5. Sharding
    6. Consistent hashing
    7. Unique IDs
    8. CAP: when the link breaks
    9. Consensus and leader election
    10. Transactions
    11. File uploads
  4. 04 Communication

    1. API styles
    2. Message queues
    3. Pub/sub and event logs
    4. Real-time updates
    5. Reliable callbacks
  5. 05 Reliability

    1. Redundancy and failover
    2. Rate limiting
    3. Timeouts and retries
    4. Observability
  6. 06 Architecture

    1. Microservices
    2. Service discovery
    3. Sagas and the outbox
    4. Batch vs stream
  7. 07 Security

    1. Authentication
    2. Authorization
    3. Encryption and secrets
  8. 08 Shipping

    1. Testing
    2. CI/CD: from commit to production
  9. 09 Whole systems

    1. From requirements to design
    2. Design a URL shortener
    3. Design a news feed
    4. Design a chat
  10. 10 Business processes

    1. Payment gateway