Delay SSO options validation until they are used

[KenHundley]

Description

Currently if you are using a SSO profile and you do not configure a ClientName or SsoVerificationCallback in your application it will always fail to execute, even if these values aren't currently necessary because of a cached SSO token.

This change allows the use of SSO Profiles without needing to add SSO specific code into the project. You can use applications like the AWS CLI v2 to authenticate and cache an SSO auth token that can then be used by any application pointing to that profile, until that token expires. This does not remove any current validations, but simply delays the validation until the values are actually needed.

Motivation and Context

This is related to the issue: #1821

Testing

I executed the Unit Tests in the solution and they all passed

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have read the README document
• I have added tests to cover my changes
• All new and existing tests passed

License

• I confirm that this pull request can be released under the Apache 2 license

[KenHundley]

Quick update. I did some additional testing today and this also removed the need to install the SSOOIDC package when using an SSO profile. Since you can do the SSO signin outside of the app, like with the aws sso login cli command, the code does not need the SSOOIDC project when using a cached token.

[boyersnet]

Thank you for this @KenHundley! We are eagerly awaiting the merge and distribution of this update to allow us to proceed with our SSO adoption.

[ashovlin]

This has been merged manually via 537a981 and released today in version 3.7.36.1 of the SDK (version 3.7.0.23 of AWSSDK.Core).

Manually marking this as closed (I don't think we preserved the commit hash when testing and building this internally, so GitHub won't autoclose).

Thanks for the contribution @KenHundley!

[boyersnet]

Thank you all! I was able to get my .net core test project to work with AWS CLI v2 sso login. I did however have to keep the AWSSDK.SSOOIDC package reference.

I have created AWSSSO.S3Buckets as a sample project for demonstration purposes.