You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS Single-Sign-On uses temporary credentials1, then uses STS to get temporary role credentials2.
naftulikay/aws-sso-env already implements the required logic to generate and export role credentials2, provided that the temporary credentials1 are present and not expired.
Temporary credentials1 are obtained via aws sso login, which opens a browser window to obtain the credentials. Config for SSO is typically stored in ~/.aws/config either as the default profile, or with INI header names like [profile prod]. Rather than storing the access key id and secret access key, the sections look like this:
Using these credentials, role credentials2 can be obtained, and then access is permitted. What is not clear at the moment is the exact logic that aws sso login uses to do the login with the browser window. If this can be determined, then aws-env can do the full lifecycle login, if not, we can only do work if valid, unexpired cached SSO credentials exist.
Support role credentials generation from cached SSO credentials.
Support aws sso login functionality to generate temporary credentials1.
The text was updated successfully, but these errors were encountered:
AWS Single-Sign-On uses temporary credentials1, then uses STS to get temporary role credentials2.
naftulikay/aws-sso-env already implements the required logic to generate and export role credentials2, provided that the temporary credentials1 are present and not expired.
Temporary credentials1 are obtained via
aws sso login
, which opens a browser window to obtain the credentials. Config for SSO is typically stored in~/.aws/config
either as thedefault
profile, or with INI header names like[profile prod]
. Rather than storing the access key id and secret access key, the sections look like this:Temporary credentials1 are stored in
~/.aws/sso/cache/$(shasum $SSO_START_URL).json
and look like this:Using these credentials, role credentials2 can be obtained, and then access is permitted. What is not clear at the moment is the exact logic that
aws sso login
uses to do the login with the browser window. If this can be determined, thenaws-env
can do the full lifecycle login, if not, we can only do work if valid, unexpired cached SSO credentials exist.aws sso login
functionality to generate temporary credentials1.The text was updated successfully, but these errors were encountered: