🎩 You're Invited:Meet the Socket team at Black Hat in Las Vegas, August 3-6.RSVP
Sign In

@vercel/passport

Package Overview
Dependencies
Maintainers
4
Versions
3
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@vercel/passport

Runtime Passport identity helpers intended for use with Vercel Functions

latest
Source
npmnpm
Version
0.1.2
Version published
Weekly downloads
10K
-55.14%
Maintainers
4
Weekly downloads
 
Created
Source

@vercel/passport

Runtime helpers for reading Passport identity inside Vercel Functions.

Usage

import { getIdentity } from '@vercel/passport';

export async function GET() {
  const identity = await getIdentity();

  if (!identity) {
    return Response.json({ authenticated: false }, { status: 401 });
  }

  return Response.json({
    authenticated: true,
    externalSubject: identity.externalSubject,
    subject: identity.subject,
  });
}

In local development, tests, or environments without Vercel request context, pass headers and cookies explicitly:

import { getIdentity } from '@vercel/passport';
import { cookies, headers } from 'next/headers';

export async function GET() {
  const identity = await getIdentity({
    cookies: await cookies(),
    headers: await headers(),
  });

  return Response.json({ identity });
}

getIdentity reads the x-vercel-oidc-passport-token header injected by Vercel after Passport validates the visitor. For tests and local debugging, you can also pass the _vercel_passport cookie explicitly.

By default, request tokens are verified against Vercel's OIDC JWKS. The helper only accepts the dedicated https://passport.vercel.com/{owner} issuer. It also validates the Passport-specific token shape so regular Vercel OIDC tokens are not accepted as Passport identities.

Local development

Local development usually does not have a real _vercel_passport cookie or x-vercel-oidc-passport-token header, because those are created by Passport in Vercel's edge network. In local development, getIdentity() returns a hardcoded Passport-shaped test identity and logs a warning the first time it does so.

The default test identity uses:

externalSubject: test-user
email: test-user@passport.local
name: Test User

Override individual fields with:

VERCEL_PASSPORT_DEV_OWNER=acme
VERCEL_PASSPORT_DEV_CONNECTOR_ID=scl_dev
VERCEL_PASSPORT_DEV_EXTERNAL_SUB=user_dev
VERCEL_PASSPORT_DEV_EXTERNAL_ISS=https://idp.example.com
VERCEL_PASSPORT_DEV_PROJECT=my-project
VERCEL_PASSPORT_DEV_PROJECT_ID=prj_local

Disable the local test identity with:

VERCEL_PASSPORT_DEV=0

or:

const identity = await getIdentity(undefined, { development: false });

Or provide the full payload yourself:

const identity = await getIdentity(undefined, {
  localIdentity: {
    typ: 'passport',
    iss: 'https://passport.vercel.com/local',
    owner: 'local',
    connector_id: 'local',
    external_sub: 'local-user',
    sub: 'owner:local:connector:local:principal:local-user',
  },
});

Development identities are ignored on Vercel unless VERCEL_ENV=development.

You can also copy a Passport token from a deployed request and pass it directly for debugging:

const identity = await getIdentity(
  { token: process.env.VERCEL_PASSPORT_TOKEN },
  { verify: false }
);

Only disable verification for local debugging. In deployed code, use the default verification behavior.

FAQs

Package last updated on 29 Jun 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts