Vercel Passport is now in Public Beta
Mirrored from Vercel — AI for archival readability. Support the source by reading on the original site.
Enterprise teams can now control access to their Vercel deployments with Vercel Passport.
Passport centralizes access using the identity providers your team already uses, like Okta, Auth0, or any compatible OIDC provider, so visitors must authenticate before they can view a protected deployment.
Use Passport to:
Reuse an OIDC application across multiple projects
Set a team default that applies to new projects automatically
Assign Passport to existing projects in bulk
After Passport authenticates a visitor, use getIdentity() from @vercel/passport to read their identity server-side:
import { getIdentity } from '@vercel/passport';import { NextResponse } from 'next/server';
export async function GET() { const identity = await getIdentity(); return NextResponse.json({ identity });}Read the Passport token server-side to identify the visitor
Passport is $100 per project per month with no limit on external users that can access a protected deployment.
Read the documentation to configure Passport from the dashboard or through the API.
Discussion (0)
Sign in to join the discussion. Free account, 30 seconds — email code or GitHub.
Sign in →No comments yet. Sign in and be the first to say something.