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
With a simple piece of code above, if a normal google user authentication is used, one could get
refresh token and also the id_token, seem from the debug screenshot:
But when an impersonated service account is used (by setting the key.json via setting GOOGLE_APPLICATION_CREDENTIALS, and the json key is got by running gcloud --impersonate-service-account [email protected] auth application-default login), there is no refresh token got and also no raw and no id_token (a JWT token) on it
Resulting in the code above prints no id_token and no JWT token can be retrieved.
Is this expected behaviour? Thanks.
The text was updated successfully, but these errors were encountered:
liufuyang
changed the title
google impersonated service account:
Cannot get id_token when using impersonated service account:
Nov 14, 2022
With a simple piece of code above, if a normal google user authentication is used, one could get
refresh token and also the
id_token
, seem from the debug screenshot:But when an impersonated service account is used (by setting the
key.json
via settingGOOGLE_APPLICATION_CREDENTIALS
, and the json key is got by runninggcloud --impersonate-service-account [email protected] auth application-default login
), there is no refresh token got and also noraw
and noid_token
(a JWT token) on itResulting in the code above prints
no id_token
and no JWT token can be retrieved.Is this expected behaviour? Thanks.
The text was updated successfully, but these errors were encountered: