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 May 12, 2026. It is now read-only.
When going through the builder, it's possible for the lifetime value to be unset (defaulting to 0 in Java).
ImpersonatedCredentialscredentials = ImpersonatedCredentials.newBuilder()
.setScopes(ImmutableList.of("some scope"))
.build();
// This builds, but has a lifetime of `0`
When we go to refresh the token, we don't check for 0. It's unclear what sending 0s for the lifetime value will do on the backend. In the above case where you don't specify a lifetime, it seems that you would be requesting the default (whether client specified or backend specified).
When going through the builder, it's possible for the
lifetimevalue to be unset (defaulting to0in Java).When we go to refresh the token, we don't check for 0. It's unclear what sending
0sfor the lifetime value will do on the backend. In the above case where you don't specify a lifetime, it seems that you would be requesting the default (whether client specified or backend specified).