[MGNLTEST-390] Saas-tf should support 'SSO token provider configuration' format for AWS sso Created: 13/Jan/23 Updated: 23/Mar/23 |
|
| Status: | Open |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Roberto Gomez | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||
| Team: | |||||||||||||
| Description |
|
Since
The profile configuration is stored by aws in the file `~/.aws/config`. And, for the case of sso there are to configuration formats:
On the other hand, saas-test-framework uses the DefaultCredentialsProvider class to lookup credentials. This class is provided by AWS Java SDK v.2, and despite some efforts to suppor 'SSO token provider configuration' so far is not working propperly. Therefore, saas-test-framework only supports 'Legacy non-refreshable configuration' format.
We need to keep track of the latest effort on the AWS SDK side to support 'SSO token provider configuration', so saas-test-frameworks can work with both configuration formats.
|