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
(node:76183) UnhandledPromiseRejectionWarning: Error: Cannot sign data without `client_email`.
at GoogleAuth.sign (/Users/calvinhuang/scale/gcptest/node_modules/google-auth-library/build/src/auth/googleauth.js:638:19)
Attempting to use workload identity federation with cloud storage signing does not work because of this, where clientLibraryConfig.json is the config retrieved from the workload identity pools page.
it is possible to work around with a bit of a hack:
The text was updated successfully, but these errors were encountered:
chingor13
added
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
labels
Jul 21, 2021
Hey @clhuang, external account creds currently do not support signing blobs. The implementation currently depends on service account keys or need the service account email in order to call signBlob which is why you are seeing this error.
I think we can update the implementation to get the service account email from the service account impersonation URL if available or otherwise error.
bcoe
added
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
and removed
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
labels
Jul 23, 2021
* feat: add GoogleAuth.sign() support to external account client
External account credentials previously did not support signing blobs.
The implementation previously depended on service account keys or
the service account email in order to call IAMCredentials signBlob.
When service account impersonation is used with external account
credentials, we can get the impersonated service account email and
call the signBlob API with the generated access token, provided the
token has the `iam.serviceAccounts.signBlob` permission. This is
included in the "Service Account Token Creator" role.
Fixes#1215
Environment details
google-auth-library
version: 7.3.0Steps to reproduce
output:
Attempting to use workload identity federation with cloud storage signing does not work because of this, where clientLibraryConfig.json is the config retrieved from the workload identity pools page.
it is possible to work around with a bit of a hack:
The text was updated successfully, but these errors were encountered: