-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix federated user ID parsing #644
Fix federated user ID parsing #644
Conversation
22022ae
to
de34f89
Compare
// The user ID is one of: | ||
// 1. UserID:SessionName (for assumed roles) | ||
// 2. UserID (for IAM User principals). | ||
// 3. AWSAccount:CallerSpecifiedName (for federated users) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How reliable it is, if this is a caller specified custom name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar to assumed role session name, although this matches the username I think. But in the case of session name it depends how its used, if you control how a role is assumed and give the credentials to someone else then you can control the session name.
197bc18
to
e70f6a8
Compare
* refactor the parsing logic to make it easier
e70f6a8
to
9fa86f7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, nckturner The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
This PR changes the way the federated user ID is treated. Instead of splitting at a colon like we do for assumed-roles, we take the whole value. This is because if we split at the colon, the user ID is just the account number and can't be differentiated from the root user.