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 }}
This repository was archived by the owner on Mar 6, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 6, 2026. It is now read-only.
service account authentication fails after 1.33.0 release #804
We also investigated the issue on our side. In our case, changing the token_uri value in the .json file helped us.
thanks, that's good to know. I would have expected the token to be signed, so that it fails when these details are changed, that's why I didn't try to change it.
Since there is no rush upgrading the package, we'll just wait for the fix and release
I can reproduce the error only when I set the "subject" filed for domain-wide delegation. Can anyone confirm if domain-wide delegation is used when you see the error?
I can reproduce the error only when I set the "subject" filed for domain-wide delegation. Can anyone confirm if domain-wide delegation is used when you see the error?
Yep, in our case the service account has domain wide delegation activated
Activity
busunkim96 commentedon Jul 19, 2021
Thanks for the report! @arithmetic1728 Could you take a look?
I think
https://oauth2.googleapis.com/tokenis the currenttoken_endpoint(see https://developers.google.com/identity/protocols/oauth2/openid-connect#discovery). Do older keys use different endpoints?busunkim96 commentedon Jul 20, 2021
Hi,
If you're experiencing this issue, please use the prior release
google-auth==1.32.1. We are working at solutions in the backend.syphar commentedon Jul 20, 2021
Thank you for the update! We already had reverted the upgrade, will wait for the next release and the fix.
Mogost commentedon Jul 20, 2021
We also investigated the issue on our side. In our case, changing the
token_urivalue in the.jsonfile helped us.syphar commentedon Jul 20, 2021
thanks, that's good to know. I would have expected the token to be signed, so that it fails when these details are changed, that's why I didn't try to change it.
Since there is no rush upgrading the package, we'll just wait for the fix and release
liuchaoren commentedon Jul 20, 2021
I can reproduce the error only when I set the "subject" filed for domain-wide delegation. Can anyone confirm if domain-wide delegation is used when you see the error?
syphar commentedon Jul 20, 2021
Yep, in our case the service account has domain wide delegation activated
busunkim96 commentedon Jul 20, 2021
Revert is under way in #808, we'll take the change again once b/194191737 is resolved.
syphar commentedon Jul 22, 2021
just tested the revert with 1.33.1, and it works (which I assumed seeing the code, but still :) )
Thank you for the quick fix!