Protected Server Components & Authenticated UI Render authenticated pages from verified request identity, not client-side guesses
Phase 17 - Supabase Authentication Volume 05 - Authentication & Security
v
v
getClaims
v
Phase 17 implements cookie-based Supabase Auth in Next.js. NestJS token verification remains Phase 18.
A protected page must verify the request, not trust presentation state Hiding a navigation link is not route protection. The request boundary and/or Server Component must derive authenticated identity from the verified session.
export const dynamic = 'force-dynamic'export default async function AccountPage() {
const supabase = await createClient()
const { data, error } = await supabase.auth.getClaims()if (error || !data?.claims) { redirect('/login') }
return <p>Subject: {String(data.claims.sub)}</p> }
v
v
v
v
The page does not trust a client-side loggedIn boolean.
When getUser is useful getClaims verifies the access token efficiently. getUser performs a network request to Supabase Auth and returns the most current user record. Use it when fresh account state matters enough to pay the network cost, such as security-sensitive session state or user-profile data that may have changed at the provider.
Authenticated UI state is not authorization A page may show the authenticated email or subject, but this does not yet decide which Workspace or Task the user can access. That becomes Phase 19 authorization and ownership.
Protected Server Components and Authenticated UI matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Protected Server Components and Authenticated UI” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: route data → UI state → component tree → interaction → accessible feedback. 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: Working TaskFlow authentication UI/session integration whose server-side checks are explicit and ready to hand tokens to NestJS.. 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.
if (query.isPending) return <TaskSkeleton />;
if (query.isError) return <TaskError retry={query.refetch} />;
if (!query.data.length) return <EmptyTasks />;
return <TaskTable tasks={query.data} />;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.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Protected Server Components and Authenticated UI” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Configure project URLs/redirects and explain why local/preview/production values differ.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Broken redirect URLs across environments
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.