v2.4.1 loops with "Cached access token appears to be stale"

[kmcduffee-verisk]

This started happening when upgraded from 2.3.1 to 2.4.1 on both MacOS and Linux. Downgrading to 2.3.1 does not cause this issue.

Cached access token appears to be stale, removing token and retrying device authorization ...

Web browser will open the following URL to begin Okta device authorization for the AWS CLI

The above repeats in a loop. The browser opens, and the usual authentication occurs, then the same message appears again and never resolves.

[AndrewWinterman]

I experience this as well

[kmcduffee-verisk]

FYI, version 2.4.0 works fine as well.

[smlx]

I was also hitting this issue. I believe it is actually an Okta API bug similar to the one described in #153, because looking at debug logs the error is the same. In any case, per #153 (comment), logging out in the browser first and then using the CLI tool's generated URL to enter the Okta login flow in the browser allowed it to successfully authenticate.

I think the real problem with okta-aws-cli here is that the message "Cached access token appears to be stale" is misleading.