Authorization Testing & Security Verification Test vertical and horizontal boundaries directly against the API
Phase 19 - Authorization, Ownership, RBAC & Permissions Volume 05 - Authentication & Security
v
v
v
Phase 19 transforms verified identity into contextual, server-side authorization decisions.
Authorization needs a test matrix, not a happy-path test OWASP recommends validating permissions on every request. That means tests should cover vertical and horizontal privilege boundaries, not just whether OWNER succeeds.
Test policy data changes too • Change a Membership role and verify the next request reflects current DB state.
• Remove membership and verify access disappears.
• Reassign a Task and verify MEMBER update rights move with the relationship.
• Attempt direct URL tampering and body-field tampering.
A hidden button can still be invoked through HTTP. The decisive tests call the API directly with different identities and resources.
Authorization decides what an authenticated identity may do to a specific resource. UI hiding is never a substitute for server-side enforcement.
Restate the goal of “Authorization Testing and Security Verification” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: trusted identity → requested action → resource scope → policy decision → allow/deny. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Permission model + guards/policies protecting TaskFlow workspace/task actions with deliberate 401/403/404 semantics.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
const canEdit =
user.role === "ADMIN" ||
(user.role === "MEMBER" && task.ownerId === user.id);
if (!canEdit) throw new ForbiddenException();Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Trace verified identity, role, resource owner/workspace, and policy inputs separately.
Add server-side resource authorization; UI visibility is only experience, never enforcement.
Without copying the final source, create a second small scenario that applies “Authorization Testing and Security Verification” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Enforce owner/member/role checks in server-side policy code.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Role strings checked inconsistently in every route
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.