Use `getIdentity()` to read authenticated visitor identity in application code after OIDC sign-in, with group claims from your provider for role-based access control.
Summary
Eliminates custom auth middleware for deployments by moving identity validation into Vercel's network layer. Developers can now enforce provider-based access control natively without managing session state or secrets in application code.
Why it matters
Eliminates custom auth middleware for deployments by moving identity validation into Vercel's network layer. Developers can now enforce provider-based access control natively without managing session state or secrets in application code.
Implementation verdict
Replaces custom OAuth/OIDC integrations for deployment-level protection. Requires Enterprise plan, Vercel Connect setup with Okta/Entra ID/OIDC provider, and SDK installation (`pnpm add @vercel/passport`). Ready now—GA release with JWT verification support for downstream services and local development fallback.
Sources
Dev Signal
Get briefs like this in your inbox — free, every weekday.
100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.