Walk the invoice authorization design
Sequence the design decisions that prevent object-level authorization failures in a new endpoint.
The endpoint GET /invoices/{id}/pdf is ready for implementation. Customers, tenant admins, and support agents may all need legitimate access. The route is simple, but the authorization boundary is not. Authorization walk Actor -> action -> object -> tenant -> response Design the decision before the code path. Each step preserves one boundary that attackers will try to cross. Shortcut requireUser + find(invoice_id) The endpoint denies by default and has tests for peers, tenants, and support context. Every protected object access needs a fresh server-side authorization decision. 01 Lookup 02 Policy 03 Response 04 Fresh case
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in