Server-Side Supabase Token Verification Using getClaims() in a NestJS 12-compatible service
Course principle: a user ID becomes trusted only after the access token has been cryptographically verified by the backend.
Why getClaims() Supabase documents auth.getClaims(jwt) as the preferred way to verify Supabase-issued JWTs. With asymmetric signing keys it verifies against the project JWKS and benefits from caching; with legacy symmetric signing it can fall back to the Auth server.
Install in apps/api cd "C:\path\to\taskflow\apps\api"
pnpm add @supabase/supabase-js@2.116.0Environment # apps/api/.env SUPABASE_URL=https://<project-ref>.supabase.co SUPABASE_PUBLISHABLE_KEY=sb_publishable_...
The publishable key is not a privileged server secret. It identifies the project/client context; the user JWT proves the caller identity. Do not use a Supabase secret/service-role key merely to verify ordinary user
access tokens.
Verification service
// auth/supabase-auth.service.ts
import { Injectable, UnauthorizedException } from '@nestjs/common'
import { ConfigService } from '@nestjs/config'
import { createClient } from '@supabase/supabase-js'@Injectable() export class SupabaseAuthService { private readonly url: string private readonly client
constructor(config: ConfigService) { this.url = config.getOrThrow<string>('SUPABASE_URL') const key = config.getOrThrow<string>( 'SUPABASE_PUBLISHABLE_KEY', )
this.client = createClient(this.url, key, { auth: { persistSession: false, autoRefreshToken: false, }, }) }
async verifyAccessToken(token: string) {
const { data, error } =
await this.client.auth.getClaims(token)if (error || !data?.claims?.sub) { throw new UnauthorizedException( 'Invalid or expired access token', ) }
const expectedIssuer = `${this.url}/auth/v1` if (data.claims.iss !== expectedIssuer) { throw new UnauthorizedException('Invalid token issuer') }
return data.claims
}
}Why extra issuer checking? getClaims() performs cryptographic verification. We still keep the expected project issuer explicit in TaskFlow so a token from another Supabase project cannot silently become an application identity.
Audience / role policy For ordinary TaskFlow users, require a user access token whose audience/role corresponds to the authenticated user context. The exact claims are read from the verified payload, never from an unverified decode. 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 “Server Side Supabase Token Verification” 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 “Server Side Supabase Token Verification” 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.Returning 403 when no valid authentication exists
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.