ImpersonatedCredentials can request 0s lifetime #526
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
When going through the builder, it's possible for the
lifetime
value to be unset (defaulting to0
in Java).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).The text was updated successfully, but these errors were encountered: