-
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
Implement an L2 for SAML providers #5320
Implement an L2 for SAML providers #5320
Comments
@eladb I think it should be in the |
Thanks @hoegertn |
Yeah I've been thinking about this. Looks like a good idea, but I don't have a good idea of what all would be involved in it. |
I think the MVP would be creating a SAML IdP from a local metadata file and being able to reference it in IAM roles as a principal in the assume role policy document. |
@eladb I would love to implement this and several other constructs for IAM but the custom resource package depends on IAM. Any wishes where I should put the constructs? Will the monocdk fix these issues? |
In those cases you can always use the custom resource provider from core: https://github.com/aws/aws-cdk/tree/master/packages/%40aws-cdk/core#the-corecustomresourceprovider-class |
L2 for [`AWS::IAM::SAMLProvider`](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-samlprovider.html). Also add derived classes for federated principals. Closes #5320 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
L2 for [`AWS::IAM::SAMLProvider`](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-samlprovider.html). Also add derived classes for federated principals. Closes aws#5320 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Implement an L2 for SAMl providers
Use Case
Proposed Solution
Implement a custom resource to create SAML providers. No CFN support available
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: