跳到正文
Vercel Blog(vercel.com)· Dima Voytenko·· 22 小時前精選AI 評分66

Vercel Connect 新增 Enterprise‑Managed Authorization 授權功能

Vercel Connect adds Enterprise-Managed Authorization

AI 導讀

導語:Vercel Connect 於公開測試階段加入 Enterprise‑Managed Authorization (EMA),允許應用在單一企業身份驗證下授權多服務,省去使用者多重授權流程。

推薦理由

Vercel Connect 以 Enterprise‑Managed Authorization 方式,讓企業可在單一身份驗證下授權多服務,減少使用者授權流程,同時支援跨應用存取與 Slack MCP 授權,提升開發效率與安全性。此功能亦可透過 Vercel Passport 取得所需範圍的存取權杖,簡化開發者在多雲環境中的身份與許可權管理。

正文 · 原文

Vercel Connect now supports Enterprise-Managed Authorization (EMA) in public beta. Your apps and agents can access supported services on behalf of signed-in users without separate consent prompts for each service.

Here's how access works:

  • Admin-managed access: Administrators can grant or revoke access to supported services through the identity provider.

  • Corporate sign-in: Users sign into your app with their corporate account through a compatible identity provider such as Okta.

  • Scoped tokens: Your app requests the scopes it needs, and Connect handles token exchange, caching, and renewal. Access is limited to approved scopes and the user’s existing service permissions.

If your app uses Vercel Passport, you can request a token for Slack’s Model Context Protocol (MCP) server with the signed-in user’s identity:

import 'server-only';

import { getToken } from '@vercel/connect';

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

export async function getResourceToken(scopes: string[]) {

const identity = await requireIdentity();

return getToken('oauth/resource', { subject: identity, scopes });

}

EMA-enabled getToken with the Passport identity

Connect supports Cross-App Access (XAA), including its use for MCP authorization through EMA. Follow the Vercel Connect EMA setup guide to configure your identity provider and services and enable EMA on their Connect connectors.

來源: Vercel Blog (vercel.com)
開啟原文