-
Notifications
You must be signed in to change notification settings - Fork 58
Description
When using AWS SSO, authentication looks for a cache file in the ~/.aws/sso/cache/ folder, but it returns a .json file that doesn't exist every time, when passed a profile, or even the default profile on the system. In order to get it to work, renaming of existing .json file to what the program is expecting is required to successfully authenticate. Tested on Windows 120722-lw-inventory-windows and MacOS 120722-lw-inventory-linux-mac
In addition, to even get to the step above, after running the aws cli to login to sso (aws sso configure) or refreshing an existing profile (aws sso login --profile named_profile), the ~/.aws/config file has to be reconfigured by hand to include SSO session details in the profile, instead of the way the aws cli builds the file, with a pointer to the sso session in the config file.