SSO cache & credentials directories inside botocore?

[nazarewk]

Describe the feature

I did not research the details, but author of https://github.com/benkehoe/aws-sso-util suggested moving my functionality of configurable SSO directories benkehoe/aws-sso-util#63 into the botocore and on the first glance it looks like a good idea.

Will add more info when i have time.

Use Case

Currently most (probably all?) of the SSO/sessions code is using in-memory credentials, requiring new credentials to be fetched for every CLI/tool invocation. Storing those values locally for reuse would help a lot with tooling responsiveness.

Proposed Solution

This is already a part of https://github.com/benkehoe/aws-sso-util/blob/master/lib/aws_sso_lib/sso.py

Other Information

Such credentials & cache could probably use the secrets management system used by the machine (keychain, secret-service etc.) possibly through https://pypi.org/project/keyring/ instead of forcing dependent SSO projects to do so themselves, like:

• https://github.com/Nike-Inc/gimme-aws-creds for Okta SSO
• https://github.com/benkehoe/aws-sso-util for AWS SSO

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

SDK version used

any

Environment details (OS name and version, etc.)

any

[tim-finnigan]

Hi @nazarewk thanks for the feature request. I think this overlaps with #1923. Have you read through the comments in that issue? If there are any distinctions between these two issues you would like to make please let us know.

[nazarewk]

looks like above feature-request indeed covers the case

[tim-finnigan]

Ok thanks for confirming, I'll go ahead and close this issue but please 👍 or comment on #1923 if you have additional feedback.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.