@vercel/connect 2.0.4 → 2.1.0

package/README.md

@@ -110,10 +110,10 @@ can import the same `connectAuthProvider` from `@vercel/connect/mcp`.
 
 ### Eve
 
-Use `connectSendblueCredentials` with Eve's native Sendblue channel. It
-resolves the app-scoped bearer token and managed sending line together, and
-includes Vercel OIDC webhook verification. When the connector has multiple
-lines, pass `fromNumber` to choose one.
+Use channel-specific credential helpers with Eve's native channels.
+`connectSendblueCredentials` resolves the app-scoped bearer token and managed
+sending line together, and includes Vercel OIDC webhook verification. When the
+connector has multiple lines, pass `fromNumber` to choose one.
 
 ```ts
 import { connectSendblueCredentials } from '@vercel/connect/eve';
@@ -124,6 +124,20 @@ export default sendblueChannel({
 });
 ```
 
+For managed Microsoft Teams bots, `connectTeamsCredentials` resolves the
+public bot application id and short-lived Bot Framework token without exposing
+the managed app's federated credential. It also verifies Connect-forwarded
+activities with Vercel OIDC.
+
+```ts
+import { connectTeamsCredentials } from '@vercel/connect/eve';
+import { teamsChannel } from 'eve/channels/teams';
+
+export default teamsChannel({
+  credentials: connectTeamsCredentials('microsoft-teams/my-agent'),
+});
+```
+
 ```ts
 import { defineMcpClientConnection } from 'eve/connections';
 import { connect } from '@vercel/connect/eve';

package/dist/eve/index.d.ts

@@ -12,6 +12,7 @@ export { connectDiscordCredentials, type ConnectDiscordCredentialsParams, } from
 export { connectGitHubCredentials, type ConnectGitHubCredentialsParams, } from './github-credentials.js';
 export { connectLinearCredentials, type ConnectLinearCredentialsParams, } from './linear-credentials.js';
 export { connectLinqCredentials, type ConnectLinqCredentials, type ConnectLinqCredentialsParams, } from './linq-credentials.js';
+export { connectTeamsCredentials, type ConnectTeamsCredentialsParams, } from './microsoft-teams-credentials.js';
 export { connectPhotonCredentials, type ConnectPhotonCredentialProvider, type PhotonCredentials, type ConnectPhotonCredentialsParams, } from './photon-credentials.js';
 export { connectSlackCredentials, type ConnectSlackCredentialsParams, } from './slack-credentials.js';
 export { connectSendblueCredentials, type ConnectSendblueCredentials, type ConnectSendblueCredentialsParams, } from './sendblue-credentials.js';

package/dist/eve/index.js

@@ -12,6 +12,7 @@ export { connectDiscordCredentials, } from './discord-credentials.js';
 export { connectGitHubCredentials, } from './github-credentials.js';
 export { connectLinearCredentials, } from './linear-credentials.js';
 export { connectLinqCredentials, } from './linq-credentials.js';
+export { connectTeamsCredentials, } from './microsoft-teams-credentials.js';
 export { connectPhotonCredentials, } from './photon-credentials.js';
 export { connectSlackCredentials, } from './slack-credentials.js';
 export { connectSendblueCredentials, } from './sendblue-credentials.js';

package/dist/eve/microsoft-teams-credentials.d.ts

@@ -0,0 +1,30 @@
+import type { TeamsChannelCredentials } from 'eve/channels/teams';
+import { type ConnectOptions, type ConnectTokenParams } from '../index.js';
+/**
+ * Token parameters accepted by {@link connectTeamsCredentials}.
+ *
+ * Mirrors {@link ConnectTokenParams}, except that Teams bot credentials are
+ * always app-scoped and must request the Bot Framework resource. `subject`
+ * and `scopes` are therefore pinned by the helper.
+ */
+export type ConnectTeamsCredentialsParams = Omit<ConnectTokenParams, 'subject' | 'scopes'>;
+/**
+ * Build {@link TeamsChannelCredentials} backed by a managed Vercel Connect
+ * Microsoft Teams connector.
+ *
+ * The helper resolves the managed bot's public application id from connector
+ * metadata and obtains short-lived Bot Framework access tokens through
+ * Vercel Connect. It never exposes the managed app's federated credential.
+ * Vercel OIDC verifies trigger-forwarded Bot Framework activities, after
+ * Connect has verified their native bearer JWT.
+ *
+ * ```ts
+ * import { connectTeamsCredentials } from '@vercel/connect/eve';
+ * import { teamsChannel } from 'eve/channels/teams';
+ *
+ * export default teamsChannel({
+ *   credentials: connectTeamsCredentials('microsoft-teams/my-agent'),
+ * });
+ * ```
+ */
+export declare function connectTeamsCredentials(connector: string, params?: ConnectTeamsCredentialsParams, options?: ConnectOptions): TeamsChannelCredentials;

package/dist/eve/microsoft-teams-credentials.js

@@ -0,0 +1,44 @@
+import { vercelOidc } from 'eve/channels/auth';
+import { getConnectorMetadata, getTokenResponse, } from '../index.js';
+const BOT_FRAMEWORK_SCOPE = 'https://api.botframework.com/.default';
+/**
+ * Build {@link TeamsChannelCredentials} backed by a managed Vercel Connect
+ * Microsoft Teams connector.
+ *
+ * The helper resolves the managed bot's public application id from connector
+ * metadata and obtains short-lived Bot Framework access tokens through
+ * Vercel Connect. It never exposes the managed app's federated credential.
+ * Vercel OIDC verifies trigger-forwarded Bot Framework activities, after
+ * Connect has verified their native bearer JWT.
+ *
+ * ```ts
+ * import { connectTeamsCredentials } from '@vercel/connect/eve';
+ * import { teamsChannel } from 'eve/channels/teams';
+ *
+ * export default teamsChannel({
+ *   credentials: connectTeamsCredentials('microsoft-teams/my-agent'),
+ * });
+ * ```
+ */
+export function connectTeamsCredentials(connector, params = {}, options) {
+    return {
+        appId: () => getTeamsAppId(connector, options),
+        tokenProvider: async () => {
+            const response = await getTokenResponse(connector, {
+                ...params,
+                subject: { type: 'app' },
+                scopes: [BOT_FRAMEWORK_SCOPE],
+            }, options);
+            return { accessToken: response.token, expiresAt: response.expiresAt };
+        },
+        webhookVerifier: vercelOidc(),
+    };
+}
+async function getTeamsAppId(connector, options) {
+    const metadata = await getConnectorMetadata(connector, options);
+    const appId = metadata.vendor.appId;
+    if (typeof appId !== 'string' || appId.length === 0) {
+        throw new Error(`Vercel Connect connector ${connector} did not return a Microsoft Teams app id.`);
+    }
+    return appId;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vercel/connect",
-  "version": "2.0.4",
+  "version": "2.1.0",
   "license": "Apache-2.0",
   "type": "module",
   "repository": {