Trusted Sources for Deployment Protection

Trusted Sources lets protected deployments accept short-lived identity tokens (OIDC) from Vercel projects and external services you authorize, so you no longer have to share a long-lived Protection Bypass for Automation secret. Trusted Sources is the recommended approach, but Protection Bypass for Automation continues to work

Callers attach an OIDC token in the x-vercel-trusted-oidc-idp-token header. Vercel then verifies the signature, checks the claims you configured, and confirms the environment matches the rule.

Link to headingAuthorize Vercel projects

By default, the Vercel OIDC token for a project can call its own deployments. To authorize another project in the same team, add it to Trusted Sources.

Self-access and cross-project rules are both customizable with from/to environment pairs. To authenticate a request from a project, forward its Vercel OIDC token:

1
import { getVercelOidcToken } from '@vercel/oidc';
2
await fetch('https://protected-project.vercel.app/api/data', {  
3
  headers: { 'x-vercel-trusted-oidc-idp-token': await getVercelOidcToken() },
4
});

Link to headingAuthorize external services

Any custom OIDC provider can be authorized as a trusted external service, such as GitHub Actions, or a Vercel project in another team.

1
- uses: actions/github-script@v7
2
  id: token
3
  with:
4
    script: |
5
      const token = await core.getIDToken();
6
      core.setSecret(token);
7
      core.setOutput('token', token);
8
- run: |
9
    curl -sSf https://protected-project.vercel.app/api/data \
10
      -H "x-vercel-trusted-oidc-idp-token: ${{ steps.token.outputs.token }}"

Read the documentation to learn more.