google-auth-library: support client-side Credential Access Boundaries (Java ClientSideCredentialAccessBoundaryFactory equivalent)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 技术栈
- google-cloud, nodejs, typescript
调研方向
首先查看 Java cab-token-generator 模块和 ClientSideCredentialAccessBoundaryFactory,然后将它们与 Node 库现有的 DownscopedClient 进行比较。确定受支持的中间令牌格式以及本地签发所需的 Node API;完成的标准是实现客户端 CAB 支持,并解决所要求的互操作性和使用行为问题。
由索引模型根据 Issue 内容生成。
描述
Feature request
Support client-side Credential Access Boundaries in google-auth-library-nodejs — the equivalent of Java's ClientSideCredentialAccessBoundaryFactory.
Background
The Node library ships the server-side DownscopedClient, which performs one STS token exchange per downscoped token. Google's IAM documentation (Create a downscoped credential) now describes the client-side approach — exchange once for an access boundary intermediary token, then mint downscoped tokens locally with varying boundary rules, no STS round trip per token — and calls it "the recommended approach because it provides better performance, scalability, and future feature compatibility."
Today that implementation exists only in Java (cab-token-generator module, ClientSideCredentialAccessBoundaryFactory). Searching the googleapis org, there is no Node, Python, or Go implementation and no open tracking issue, so filing this one for Node.
Use case
A token broker minting many unique prefix-scoped Cloud Storage tokens at high frequency: per-tenant object-name prefixes, one short-lived token per tenant session. With the server-side DownscopedClient, every unique boundary costs an STS exchange against the sts.googleapis.com token-exchange quota (6,000/project/minute). Caching per tenant helps, but fresh-mint demand scales with distinct active tenants; client-side minting removes the ceiling entirely, as the docs note.
Questions
- Is client-side CAB support planned for
google-auth-library-nodejs? Any timeline? - If it is not planned soon: is the intermediary-token wire format (the protobuf-encoded boundary + encryption scheme visible in Java's
cab-token-generator) considered stable and supported for third-party client implementations, or is it internal and subject to change?
Environment
google-auth-library 10.x on Node 24 / Bun, tokens consumed by Cloud Storage JSON/XML APIs.
- 主要语言
- TypeScript
- 星标
- 3.2k
- 派生
- 732
- 平均合并
- 2 天 11 小时
- 30 天内合并 PR
- 99
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
googleapis/google-cloud-node 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
googleapis/google-cloud-node#9854 ·
维护者通常 1 天内回复
-
pubsub: "Operation attempted on ended Span" when a modack is flushed after the message was acked未关闭api: pubsub
难度 2/5 1-3 小时 新手友好度 82/100
googleapis/google-cloud-node#9853 ·
维护者通常 1 天内回复
-
storage: V4 getSignedUrl sorts canonical headers with localeCompare, so they disagree with X-Goog-SignedHeaders可能已有人在做 @itsrayeedscodespace 于 9 天前认领。 未关闭api: storage
难度 2/5 1-3 小时 新手友好度 82/100
googleapis/google-cloud-node#9840 · 1 条评论 ·
维护者通常 1 天内回复
-
firestore: getPartitions() emits gax AutopaginateTrueWarning in every process可能已有人在做 @TheRealDanii 于 13 天前认领。 未关闭api: firestore
难度 2/5 1-3 小时 新手友好度 76/100
googleapis/google-cloud-node#9736 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
googleapis/google-cloud-node#9723 ·
维护者通常 1 天内回复
查看 googleapis/google-cloud-node 的全部 Issue
相似的 Issue
-
bot:ai-assisted component:platform-js status:untriaged
难度 1/5 1 小时以内 新手友好度 74/100
midnightntwrk/platform-js#38 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
ranxianglei/billion-context#7068 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
mybigday/whisper.rn#348 ·
-
enhancement severity:low
难度 2/5 1-3 小时 新手友好度 82/100
Battle-Cattle/BCUK-Bot-4#1075 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
ilan-pinto/roaring-lions#1552 ·
维护者通常 1 天内回复