Add support for AWS SSO profiles #549

itsdalmo · 2020-03-31T12:07:10Z

This PR hopefully closes #449 by adding support for AWS SSO.

Given a AWS SSO Profile configuration in ~/.aws/confg:

[profile Administrator-123456789012]
sso_start_url=https://aws-sso-portal.awsapps.com/start
sso_region=eu-west-1
sso_account_id=123456789012
sso_role_name=Administrator

This PR allows aws-vault to obtain short lived credentials for an SSO profile, which can be used by e.g. exec (and login), and produces output as seen below:

$ aws-vault exec Administrator-123456789012 -- aws sts get-caller-identity

Attempting to automatically open the SSO authorization page in your default
browser. If the browser does not open or you wish to use a different device to
authorize this request, open the following URL:

https://device.sso.eu-west-1.amazonaws.com/?user_code=HZZB-FPRL
(Use Ctrl-C to abort)

{
    "UserId": "AROAWH...",
    "Account": "123456789012",
    "Arn": "arn:aws:sts::123456789012:assumed-role/AWSReservedSSO_ReadOnly_f4296a2ab1f54217/..."
}

In the above example, aws-vault would take care of:

Creating and registering a new AWS SSO client (one per unique sso_start_url in your config).
Initiating the client authorization flow in AWS SSO (and opening the default browser for the user).
Creating a new access token after the client has been authorised by the user.
Creating a new temporary session for the exec command.

The client credentials (ID and secret), access token and session credentials will all be cached in the Keyring, and automatically refreshed (by repeating the relevant steps above) when they expire. The AWS SSO Client is valid for 3 months by default, while the access token and session expiration depends on the settings for your AWS SSO Organization.

Please take a look and let us know what you think 😅

Co-authored-by: Rickard Löfström <[email protected]>

statik · 2020-04-01T04:12:09Z

vault/ssorolecredentialsprovider.go

+
+ for {
+ // Sleep to allow the user to complete the login flow
+ time.Sleep(3 * time.Second)


I wonder about this delay, should it be configurable? I am not very fast on the keyboard, it could definitely take me longer than 3 seconds to enter my credentials in AWS SSO via my 3rd party IdP, including finding my MFA device and completing the authentication. Or is it that the user should already be logged into the browser ahead of time and this time is for clicking a single approve button?

Just to clarify, retries every 3 seconds. If you have a SSO session against your IDP, it might not require you to re-authenticate with the MFA, so waiting longer might be annoying as it’s almost instant after the first initial authentication.

I did some digging around to see how the AWS CLI does this, and ended up here: https:/boto/botocore/blob/v2/botocore/utils.py#L1663

And from their comments around the default retry interval and slow down delay:
https://tools.ietf.org/html/draft-ietf-oauth-device-flow-15#section-3.5

I.e., we (like the AWS CLI) should just be using the interval that is specified in the response from the API when calling StartDeviceAuthorization, and fall back to the 5s defaults defined by the RFC. d7ce500 implements this, and also adds handling for the SlowDownException error code.

From my testing, this has effectively reduced the retry interval to 1s, which makes AWS Vault more snappy to respond after I had completed the browser login.

statik · 2020-04-01T04:21:04Z

I've tested this branch with my AWS SSO configured to use a 3rd Party IdP (Google Apps SAML), and it works well so far 😍

itsdalmo · 2020-04-06T12:58:51Z

Hi @mtibben! Sorry to ping you like this; I was wondering when you might have time to look at this PR (since you seem to be the one maintaining aws-vault these days) - do you need anything else from us before reviewing and/or merging the PR?

mtibben · 2020-04-16T11:04:14Z

vault/ssorolecredentialsprovider.go

+ return nil, err
+ }
+
+ fmt.Printf(authorizationTemplate, aws.StringValue(auth.VerificationUriComplete))


If we dump this to stdout with fmt.Printf it may interfere with the output of whatever command you're executing... can we get this output to stderr, preferably through kingpin somehow? Alternatively should we be using the prompt driver to achieve this?

Great catch! Since prompt is only used for requesting user input (which we are not doing here), and kingpin is not currently used anywhere outside the cli/ page right now, I think it makes most sense to use Fprintf(os.Stderr, ...) here.

mtibben · 2020-04-16T11:06:34Z

vault/ssorolecredentialsprovider.go

+
+ expiration := aws.MillisecondsTimeValue(resp.RoleCredentials.Expiration)
+
+ // This is needed because sessions.Store expects a sts.Credentials object.


yes I'm hoping to refactor sessions.Store completely and turn it into an ordinary Provider

mtibben · 2020-04-16T11:12:33Z

vault/ssorolecredentialsprovider.go

+ }
+ return &SSOAccessToken{
+ Token: aws.StringValue(t.AccessToken),
+ Expiration: time.Now().Add(time.Duration(aws.Int64Value(t.ExpiresIn)) * time.Second),


Can we break this up to make it more readable?

mtibben · 2020-04-16T11:13:20Z

USAGE.md

@@ -222,6 +222,25 @@ role_arn = arn:aws:iam::123456789012:role/target

 You can also set the `mfa_serial` with the environment variable `AWS_MFA_SERIAL`.

+## AWS Single Sign-On (AWS SSO)


Add this to the TOC at the top

mtibben · 2020-04-16T11:16:51Z

vault/ssorolecredentialsprovider.go

+)
+
+// CachedSSORoleCredentialsProvider uses the keyring to cache SSO Role sessions.
+type CachedSSORoleCredentialsProvider struct {


Hmm I was planning a sessions refactor, but it may need to encompass this. Mind if I ping you if I get to this?

mtibben · 2020-04-16T11:23:46Z

vault/ssorolecredentialsprovider.go

+ retryInterval = time.Duration(i) * time.Second
+ }
+
+ for {


Would it be possible to capture the retry logic in its own separate function? There's an example of this in

aws-vault/cli/rotate.go

Line 149 in 877981b

func retry(maxTime time.Duration, sleep time.Duration, f func() error) (err error) {

mtibben · 2020-04-16T11:25:40Z

This is fantastic, thank you @itsdalmo!

I know from experience that testing this stuff is really really hard as you basically have to mock out everything. But if there are any simple tests you can write to prevent me breaking this going forward that would be ideal

Co-authored-by: Kristian Dalmo Olsen <[email protected]>

glenjamin · 2020-12-14T12:07:18Z

Does anyone have this working with credentials_process?

edit: I've been able to get this to work with credentials process and terraform by having two profiles:

[profile xyz]
region=us-east-1
credential_process=aws-vault exec --json xyz-sso

[profile xyz-sso]
sso_start_url = https://someone.awsapps.com/start
sso_region = us-east-1
sso_account_id = 045464924556
sso_role_name = TheRole
region = us-east-1

Add support for AWS SSO profiles

01e8d5a

Co-authored-by: Rickard Löfström <[email protected]>

statik reviewed Apr 1, 2020

View reviewed changes

Fix retry interval for device authorization

d7ce500

mtibben reviewed Apr 16, 2020

View reviewed changes

feat: pipe instructions to stderr

12bcb60

Co-authored-by: Kristian Dalmo Olsen <[email protected]>

mtibben merged commit d75001a into 99designs:master Apr 21, 2020

This was referenced Apr 21, 2020

SAML-based authentication using AssumeRoleWithSAML #235

Closed

ATTENTION: aws-okta is on indefinite hiatus segmentio/aws-okta#278

Closed

rickardl mentioned this pull request Apr 21, 2020

Add unit tests for AWS SSO provider #563

Merged

mtibben added this to the v6 milestone Apr 30, 2020

This was referenced Jun 6, 2020

Problem when using sops (mozilla/sops) flyinprogrammer/aws-sso-fetcher#6

Closed

Feature: Execute 'aws sso login' when cached token is expired flyinprogrammer/aws-sso-fetcher#4

Closed

kapilt mentioned this pull request Aug 7, 2020

Support AWS CLI v2 AWS Single Sign-On hashicorp/terraform-provider-aws#10851

Closed

ldormoy mentioned this pull request Sep 4, 2020

Provide way to get current credentials (AWS SDKs do not support SSO) aws/aws-cli#5261

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add support for AWS SSO profiles #549

Add support for AWS SSO profiles #549

itsdalmo commented Mar 31, 2020

statik Apr 1, 2020

rickardl Apr 1, 2020 •

edited

Loading

itsdalmo Apr 1, 2020

statik commented Apr 1, 2020

itsdalmo commented Apr 6, 2020

mtibben Apr 16, 2020

itsdalmo Apr 17, 2020

mtibben Apr 16, 2020

mtibben Apr 16, 2020

mtibben Apr 16, 2020

mtibben Apr 16, 2020

mtibben Apr 16, 2020

mtibben commented Apr 16, 2020

glenjamin commented Dec 14, 2020 •

edited

Loading


		expiration := aws.MillisecondsTimeValue(resp.RoleCredentials.Expiration)

		// This is needed because sessions.Store expects a sts.Credentials object.

		@@ -222,6 +222,25 @@ role_arn = arn:aws:iam::123456789012:role/target

		You can also set the `mfa_serial` with the environment variable `AWS_MFA_SERIAL`.

		## AWS Single Sign-On (AWS SSO)

Add support for AWS SSO profiles #549

Add support for AWS SSO profiles #549

Conversation

itsdalmo commented Mar 31, 2020

Choose a reason for hiding this comment

rickardl Apr 1, 2020 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

statik commented Apr 1, 2020

itsdalmo commented Apr 6, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mtibben commented Apr 16, 2020

glenjamin commented Dec 14, 2020 • edited Loading

rickardl Apr 1, 2020 •

edited

Loading

glenjamin commented Dec 14, 2020 •

edited

Loading