Skip to content

Home

Jump to bottom
Victor San Kho Lin edited this page Jul 18, 2022 · 8 revisions

Release 1.0.0 Notes

With yawsso-v1.0.0 release, the code base has been made especially improvement in terms of security aspect. Part of security revamp, this repo main branch git history has been rewritten to address some 3rd parties (both public and private) DevSecOps scan and reports such as GitGuardian, TruffleHog, Detect Secrets, LGTM, CodeQL, CodeClimate, some internal scans, etc. Here is tweet.

  • If you have forked this repo without any major changes made at your copy then I'd recommend to just simply delete and re-fork it.
  • If you have some changes and, no upstream PR made then I'd recommend to make a git diff your changes, then delete your copy, re-fork and re-apply your patch on top of the newer code base.
  • Apology for inconvenience. But. I had to make this tool to be able to be usable in some strict environment.

This won't apply to normal yawsso CLI user who do not need to touch the source code at all. Simply enjoy the new-improved program. 🙂

-victor

Upstream Tracking

Boto3

  • Tested 2020-06-15
  • Seem like the following Boto3 version work with SSO session and credentials process by default.
boto3==1.14.2
botocore==1.17.2

Why

AWS CLI v2 SSO login cache/store credentials is somewhat different to AWS CLI v1 i.e. no longer in ~/.aws/credentials. There are many SDK and tools still depends on this legacy ~/.aws/credentials format.

And, https://github.com/aws/aws-cli/issues/4982 in CLI repo itself!!

This tool is originally based on aws_sso.py script but take different approach and depends only on AWS CLI v2 for get-role-credentials. Well, everything else fail (including boto3) except CLI itself, so... ☝️

Someday, we won't need this anymore. But, until then this tool sync up AWS CLI v2 SSO login session to legacy format auto-magically!!

Others

If this tools is not working for you, try the following.

AWS SSO

AWS STS - SAML with screen scraping

Clone this wiki locally