feat(rt): standalone sso credentials provider #462
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.








Issue #
#252
Description of changes
aws-configto embed a custom SSO service (trimmed down with only the required operation to implement the provider)CachedCredentialsProviderto be implemented in KotlinIMPORTANT: This provider is NOT yet integrated into the default chain or the profile provider. You must instantiate it directly to use it. See #461
e.g.
Tested by setting up SSO per the directions, using the CLI to configure/initiate the login flow, and testing against STS
GetCallerIdentity.* NOTE: The AWS SSO service can act as an identity provider so there is no need to setup an external one. Just turn on AWS Organizations, enable SSO, add a user, and it should be usable.
Should see the SSO role and user in the output.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.