`taskcluster signìn` integration doesn't extend expiration
Closed this issue · 3 comments
jonasfj commented
If the .../cli
client exists and is expired, it just rotates the accessToken and that's it... The client I get back is still expired..
Note: We do set deleteOnExpiration
, but I'm pretty sure that taskcluster-auth
still waits a few days after expiration before deleting clients.
djmitche commented
@helfi92 just wrote code to also update the expiration date. I don't know if that's landed yet, given the change freeze?
jonasfj commented
ah, awesome :)