-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
iam: SAML principal AssumeRoleAction is hardcoded #29456
Comments
Do you have any public document link about this? We probably need to update here aws-cdk/packages/aws-cdk-lib/aws-iam/lib/principals.ts Lines 741 to 752 in 0c73143
|
There is an example in the docs here for implementing ABAC using tags and SAML IdP integration: https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_abac-saml.html For Quicksight, it has it in their docs to add |
I'll take this. |
@justin8 I think you should be able to use EDIT: ignore this..not right. |
I did the same thing :) I tried that thinking it sounded correct, then ended up reading through the code to see that it wouldn't work |
Try adding const federationRolePrincipal = new iam.SamlPrincipal(samlProvider, {
StringEquals: { 'SAML:aud': 'https://signin.aws.amazon.com/saml' },
}).withSessionTags(); |
Ah! Thank you, you're right that does fix the issue, I must've missed that function. |
|
Describe the bug
Currently when defining an assume role policy on a role the action is hardcoded to
sts:AssumeRoleWithSAML' [here](https://github.com/aws/aws-cdk/blob/v2.132.0/packages/aws-cdk-lib/aws-iam/lib/principals.ts#L746). However for some use cases, such as Quicksight's own SAML integration, you also need
sts:TagSession` in order to use the email sync feature.Expected Behavior
You should be able to modify the assume role action and just have a default, not a hardcoded action.
Current Behavior
It's hardcoded and requires the use of escape hatches such as:
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.126.0
Framework Version
No response
Node.js Version
18
OS
Linux
Language
TypeScript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: