Closed diranged closed 4 months ago
Um. That's weird. "expiresAt": "2023-03-16T15:11:53.540Z"
looks alright -- But. I will double check, soon. Thanks for reporting in.
Same problem here.
@victorskl the datetime value is fine. The issue is with the pattern which doesn't expect milliseconds; %Y-%m-%dT%H:%M:%SZ
. Removing the millisecond part from the value (in the cached file) resolves the issue. The pattern seem to need an optional milliseconds part.
Right..! Mine is like
{
"startUrl": <snip>,
"region": "ap-southeast-2",
"accessToken": <snip>,
"expiresAt": "2023-08-04T06:15:57Z",
"clientId": <snip>,
"clientSecret": <snip>,
"registrationExpiresAt": "2023-10-12T02:27:45Z",
"refreshToken": <snip>
}
Thanks for detective work. I will fix/support/work on this..!
Started experiencing this for the first time ever this morning. Strange I have not seen it before.
I refreshed my SSO session and the issue went away.
This issue is now found to be related with https://github.com/victorskl/yawsso/issues/90
I'm probably going to handle this expiry check differently. And not to rely on this expiresAt
field. Stay tune for RC.
It should fix with 1.2rc1. Let me know any feedback, if any.
pip install -U yawsso==1.2.0rc1
yawsso --version
yawsso 1.2.0rc1
The yawsso-1.2.0 out.!
Sorry for year long wait. This should be fixed. The yawsso does not check this expiresAt
field anymore.
pip install -U yawsso==1.2.0
It should attempt auto-refresh as long as the refresh token lives...
Better yet, try auto
subcommand; this will auto login as last resort when the refresh token itself has expired...
yawsso auto --profile dev
Ran into this weird one.. I'm running
yawsso
on a cron in the background and I noticed it wasn't executing. Here are the logs:Here's the sso cache'd cred file:
And the AWS CLi ver: