Vercel Passport is now generally available
- Source
- vercel.com
- Author
- Andrew Qu
- Date

Context
Vercel Passport lets a deployment use an organization's identity provider to authenticate visitors before they reach the application. The general-availability announcement explains that application code can then read the verified visitor identity through getIdentity(), rather than trusting identity information supplied by the browser.
The application still decides what that visitor may do. For group-based access, administrators must request the groups scope and the corresponding claim; application code then checks the returned membership. Passport supplies verified identity information that developers can use to enforce access rules.
- tool permissions — The rules governing which tools an agent may call and which need confirmation — the boundary between a mistake and an incident.
- token — The chunk of text a model reads and writes in — roughly three-quarters of a word — and the unit AI usage is billed in.
“Visitors authenticate through Okta, Microsoft Entra ID, or any OIDC provider before viewing a protected deployment, and Vercel forwards a signed identity token to the deployment so application code can build on who the visitor is.”
“Vercel strips client-supplied values for the x-vercel-oidc-passport-token header and injects the verified token after Passport validates the session, so the identity your code receives is already verified.”
“The helper returns null only when a request arrives without a Passport session, because unauthenticated browser visitors are redirected to the identity provider before they ever reach your code.”
Checking sign-in…
Loading comments…





