Ben Kehoe

I'd still love to see it!

I'm nearing the end of my time off, and I plan on fully re-engaging with all of my projects, but realistically it means nothing is going to be addressed until...

Ok, let's see. Trying to do this after a long day at re:Inforce, so let me know if any of this makes sense. A "profile" is a set of configuration...

Identity Center has a region associated with it, which is distinct from the region credentials retrieved from Identity Center (in that Identity Center region) are used in. `AWS_DEFAULT_REGION` is the...

I'm skeptical this is a problem with aws-sso-util, the credential process is compliant with the spec. The JS SDK v2 has slowly been fixing its Identity Center support, I wouldn't...

I'm nearing the end of my time off, and I plan on fully re-engaging with all of my projects, but realistically it means nothing is going to be addressed until...

Finally back to this. I think the right way to solve this is to spread out the calls to match the right API rate limit. Do we know what that...

Well that is weird. Is it something that you can reproduce? It appears that your token didn't have an `expiresAt` field in it, which should always be present (so there's...

Use `-vvv` which will turn on all debug logging. When it's working correctly, check the files in `~/.aws/sso/cache`, one of them should have your token in it (along with an...

Huh. Does that cache entry work with the AWS CLI, e.g. `aws sts get-caller-identity`? It does seem like it should ([code link](https://github.com/boto/botocore/blob/82aee347f401804eb9576fee36de19d2348a466b/botocore/utils.py#L3103))