Support workload identity federation for plugin credentials
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 25/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- aws, azure, gcp, typescript
調査の方向性
Start with packages/junior-plugin-api/src/manifest.ts, chat/pi/gateway-auth.ts, and the existing grantForEgress/issueCredential lease path referenced in the issue. Read how plugin credentials are declared and how host egress caches leases. The issue is done when plugins can declare a host-minted, refreshed federated credential with a configurable header and the stated security controls, with GCP as the first exchange provider.
索引モデルが issue の本文から書いたものです。
説明
Plugins cannot authenticate to services that need short-lived credentials issued to a workload, such as apps behind Google Cloud IAP. Vercel issues per-deployment OIDC tokens that GCP (and AWS/Azure) can trust through workload identity federation, so no long-lived cloud key is needed. Junior has no shared primitive for this.
Current behavior
- Manifest
credentialssupport onlyoauth-bearer(packages/junior-plugin-api/src/manifest.ts): a token from a host env var or per-user OAuth, injected for the listed domains.api-headersare static values with env refs. - Packaged plugins can issue short-lived header leases with
grantForEgress+issueCredential(the GitHub plugin does this). Host egress caches a lease until itsexpiresAt. - Core uses Vercel OIDC only for AI Gateway auth (
chat/pi/gateway-auth.ts) and for verifying sandbox egress requests. Plugins have no way to get the deployment's OIDC token, and there is no shared GCP token exchange.
Gap
- IAP needs a Google-signed credential that is valid for at most 1h. A static env token cannot work. The only option today is a JSON service account key in env, which is the long-lived secret that federation removes.
- Every plugin that needs this must rebuild Vercel OIDC → Google STS → IAM Credentials, with its own caching and security checks.
- Some upstreams use
Authorizationfor their own auth (Redash:Authorization: Key …). The proxy credential then has to go inProxy-Authorization, which IAP supports. Manifest credentials cannot choose the header today.
Capabilities identified in design discussion
- Host workload identity exchange: a plugin credential trades the deployment's Vercel OIDC token for a short-lived cloud credential. GCP first: STS exchange, then IAM Credentials (
signJwt,generateIdToken,generateAccessToken) on one named service account. - Declared in
plugin.yaml: a plugin such as Redash should need no code. Inputs: domains, workload identity provider audience, service account, token kind and audience (for example an IAP service-account JWT withaud: https://<host>/*), and target header. - Configurable target header, including
Proxy-Authorization, used alongside staticapi-headers. - Lease caching and refresh before expiry, through the existing egress lease path.
- Security invariants:
- Mint only on the host. Never expose the token to the sandbox or the model.
- No long-lived cloud keys.
- Document the provider attribute condition that limits trust to production deployments (
sub = owner:<team>:project:<project>:environment:production), because team members can pull development OIDC tokens locally. - Emit telemetry for each mint.
Motivating case
An internal Redash instance behind Google Cloud IAP. IAP accepts JWTs signed by a service account with aud set to the app URL, and accepts them in Proxy-Authorization (IAP programmatic auth). This works even when IAP uses the Google-managed OAuth client. Vercel documents the GCP federation setup in Connect to GCP.
via @dcramer.
--
- 主要言語
- TypeScript
- スター
- 397
- フォーク
- 43
- 平均マージ
- 8時間 28分
- マージ済み PR(30日)
- 764
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
getsentry/junior のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 64/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
メンテナーはふだん 1 日以内に返信
getsentry/junior の issue をすべて見る
似ている issue
-
area:tooling good first issue
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
interledger/publisher-tools#1007 ·
メンテナーはふだん 1 日以内に返信
-
priority/medium roadmap/v1.1.1 stakeholder/rapr type/bug
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
databrickslabs/ontos#1420 ·
メンテナーはふだん 3 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
vercel-labs/just-bash#756 ·
メンテナーはふだん 1 日以内に返信
-
area: ci good first issue
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
interledger/web-monetization-extension#1555 ·
メンテナーはふだん 1 日以内に返信
-
🐞 bug 🧐 unconfirmed
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
Tencent/tdesign-vue-next#7056 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信