You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4e5a0d0
Browse filesBrowse the repository at this point in the historyBrowse files
docs(auth): clarify quota project behavior on ImpersonatedCredentials (#14597)
Fixes#12604
### Summary
Clarifies the Javadoc on `ImpersonatedCredentials`
(`Builder.setQuotaProjectId`, `idTokenWithAudience`, and `create`
overloads) regarding how `quotaProjectId` is applied:
- The `quotaProjectId` configured on `ImpersonatedCredentials` is sent
via the `x-goog-user-project` header on **downstream API requests**
authenticated with the impersonated credentials.
- Requests to the IAM Credentials API (`generateAccessToken` and
`generateIdToken`) used to mint tokens are authenticated using
`sourceCredentials`. To specify a quota project (`x-goog-user-project`
header) for those IAM Credentials API calls, the quota project ID should
be configured on `sourceCredentials`.
0 commit comments