NestJS Guard & Protected API Mental Model Understand the future token-verification boundary before implementing it
Phase 16 - Authentication Fundamentals Volume 05 - Authentication & Security
v
v
v
Phase 16 builds the security mental model before any Supabase Auth integration code is introduced.
The NestJS guard is a verification boundary Phase 18 will implement the guard, but the mental model belongs here. The guard runs before protected controller logic and either establishes a trusted authenticated subject or rejects the request.
v
v
v
v
v
v
A decoded token does not reach business logic until verification succeeds.
Typical API outcomes Condition Result
Do not confuse authentication with role checks The authentication guard should establish who the caller is. Authorization logic can then evaluate workspace membership, ownership, role, or permissions. Keeping these concerns separable makes policy easier to reason about and test.
Request -> AuthGuard: who are you? -> Authorization/Service: may you do this? -> Business rule: is this operation valid? -> Prisma/PostgreSQL
In real applications you must choose whether routes are protected by default with explicit public exceptions, or public by default with explicit guards. Security-sensitive systems generally benefit from fail-closed thinking: it should be harder to accidentally expose a new route.
Log request IDs and authentication outcomes, not raw access tokens.
NestJS structure becomes valuable when the request pipeline and responsibility of controllers, services, guards, pipes, and providers are explicit rather than magical.
Restate the goal of “NestJS Guard and Protected API Mental Model” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: HTTP request → Fastify adapter → Nest pipeline → controller → service → response. 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: Authentication threat/flow diagram explaining what the browser stores, what servers verify, and what happens when credentials expire.. 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.
@Controller("tasks")
export class TasksController {
constructor(private readonly tasks: TasksService) {}
@Get()
findAll() {
return this.tasks.findAll();
}
}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.
Read the constructor index in the error, then check provider registration, module imports, and exports in that order.
Confirm method/path, controller registration, global prefix, and guard/pipe behavior using request logs.
Without copying the final source, create a second small scenario that applies “NestJS Guard and Protected API Mental Model” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Explain secure/httpOnly/sameSite cookie attributes and when browser JS should not read a token.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Treating base64 JWT content as proof of authenticity
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.