google-auth-library: support client-side Credential Access Boundaries (Java ClientSideCredentialAccessBoundaryFactory equivalent)

未关闭
#8,855 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 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
  1. Is client-side CAB support planned for google-auth-library-nodejs? Any timeline?
  2. 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

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

googleapis/google-cloud-node 的其他 Issue

查看 googleapis/google-cloud-node 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。