megachangelog
Announcement

Vercel Passport is now in Public Beta

Vercel Passport enables enterprise teams to control deployment access using their own identity provider (Okta, Auth0, OIDC-compatible). Visitors authenticate before viewing protected deployments, and Vercel injects a signed JWT into request headers for server-side identity verification.

Enterprise teams can now control access to their Vercel deployments with , using their own identity provider.Vercel Passport

Visitors authenticate through providers like Okta, Auth0, or any compatible OIDC provider before they can view a protected deployment.

Use Passport to:

After Passport authenticates a visitor, Vercel injects a signed JWT into the request header. Read it server-side to access the claim, the stable visitor identifier returned by your identity provider:x-vercel-oidc-passport-tokenexternal_sub

Read the to get started.documentation

Read more

  • Reuse an OIDC application across multiple projects

  • Set a team default that applies to new projects automatically

  • Assign Passport to existing projects in bulk

authenticationsecurityidentityenterpriseaccess-control

Source: original entry ↗