mufassall

Security / 2 / 3

Authorization

Knowing who the caller is does not tell you what they may do. An invoicing app shared by many companies learns this the hard way: changed ids in the URL, forgotten checks, and a service account that could do anything.

  • 12 min
  • Intermediate
  • 10 steps
Foreign records read
0 /day
API p95
45 ms
Job permissions
—
Open in Lab
  • request
  • reply
  • redelivery
  • duplicate
  • lost

Numbers are a model scenario, not measurements

The real request

Web app → Invoice API

Request

GET /invoices/inv_1042 HTTP/1.1
Host: api.example.com
Authorization1: hidden

Response

HTTP/1.1 200 OK
{
  "id": "inv_1042",
  "company_id": 2"c_7",
  "amount": 1250000,
  "status": "approved"
}
  1. Authorization · hidden — Alice's access token. It proves who she is, nothing more. Hidden here.
  2. company_id — The invoice belongs to company c_7. The API never compared this to Alice's company.
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