Signing Keys, JWKS, Rotation and 2026 Supabase Choices Understanding what getClaims() is doing for you
Course principle: a user ID becomes trusted only after the access token has been cryptographically verified by the backend.
Modern Supabase signing keys Supabase now supports asymmetric signing keys and publishes trusted public keys through the project JWKS endpoint. Public keys verify tokens but cannot mint new ones. GET https://<project-ref>.supabase.co/ auth/v1/.well-known/jwks.json
Why getClaims() fits this course Concern getClaims() behavior
Alternative: direct jose verification For projects committed to asymmetric signing keys, a backend can use a JWT library such as jose with a remote JWKS and explicitly validate issuer, audience and expiration. Supabase documents this pattern. We do not choose it as the primary course implementation because getClaims() also handles legacy signing-key projects.
@supabase/server in 2026 Supabase now recommends @supabase/server for bearer-token backend APIs and ships a NestJS adapter. Version 1.x is public beta. At the time of this phase, the package adapter table lists NestJS 10 and 11, while TaskFlow is NestJS 12. We therefore use the framework-independent verification path and can revisit the adapter after its published compatibility catches up.
Revocation nuance JWKS caching improves performance but means emergency signing-key revocation can have a cache window in external backend verifiers. Supabase documents this trade-off; incident-response plans should account for it. Source note: verified against current Supabase Auth/getClaims/signing-key guidance and NestJS authentication/authorization docs. Full URLs and version notes are included in SOURCE_NOTES.txt.
Authentication answers who the request represents. Treating decoded or client-supplied identity as trusted is a security boundary failure.
Restate the goal of “Signing Keys JWKS and 2026 Supabase Choices” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: credentials/session → token → verification → trusted identity → protected operation. 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 guard + verification service + current-user helper + protected /auth/me and task routes.. 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 token = readBearerToken(request);
const claims = await verifier.verify(token);
request.user = {
id: claims.sub,
email: claims.email,
};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.
Inspect whether a token exists, whether it is expired, which issuer/audience signed it, and what the API verifier expects.
Trust only verified server claims; never repair identity by accepting a client-sent user id.
Without copying the final source, create a second small scenario that applies “Signing Keys JWKS and 2026 Supabase Choices” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Verify the token server-side using the supported Supabase/JWT verification path.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Trusting userId from request body/query
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.