Allow use of aws-lc-rs instead of ring for the aws-config sso feature flag

[jarbaugh8]

Describe the feature

The aws-config sso feature flag currently requires the ring dependency.

The rest of this crate has switched to using aws-lc-rs instead of ring by default, though users can still use ring with some additional configuration.

It would be nice if the crypto crate used by the aws-config sso feature flag were configurable in some way to pick between aws-lc-rs and ring (or maybe it could somehow inherit this from the HTTPS client configuration).

Use Case

I'm trying to use a single crypto provider in my application, and I've standardized on aws-lc-rs. Even though this use of ring is not very substantial (and might not be meaningful from a FIPS compliance perspective), having it in my dependency tree makes it harder to verify if this is the only use of ring in my application, as many other crates may have ring as their default.

Proposed Solution

No response

Other Information

No response

Acknowledgements

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

A note for the community

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue, please leave a comment

[landonxjames]

Looks like the use is minimal and we are just keeping it around for a SHA1 calculation? We are using the sha1 crate to calculate SHA1 in aws-smithy-checksums and we could probably use that here as well.

Would likely be a simple update if you are willing to cut a PR for it.

[jarbaugh8]

Awesome, I'll plan on doing that later this week.