We have to think about to connect our internal Crowd directory to AWS IAM services to use our internal credentials in the AWS ressources. Does anybody have any experiences about this topic to implement this configuration?
Utoolity is offering an add-on family Identity Federation for AWS which implements an Identity Broker that provides Federated AWS access for Atlassian users, i.e. it allows to Add long-term AWS security credentials (IAM users) once and configure AWS access for Atlassian groups with temporary credentials and fine grained permissions via IAM Policies thereafter - this yields the following cross product features (on top of product specific ones):
The add-on is conceptually designed and implemented as a cross product solution, however, the Atlassian Marketplace does not support commercial cross product add-on, which is why we need to offer it separately per product.
The main usage at this point is to provide the IAM based AWS security credentials backing for Tasks for AWS (where it is included for free, see our resp. FAQ Do I need an Identity Federation for AWS license when using it from another Utoolity add-on like Tasks for AWS?).
That being said, we always considered its Identity Broker capabilities to be a notable standalone use case too, and we have several customers who indeed simply use Identity Federation for AWS as is to provide SSO to the AWS Management Console without the need to manage individual AWS credentials per user.
Identity Federation for AWS (JIRA) work just fine with all common Crowd/JIRA integration scenarios outlined in Connecting to Crowd or Another JIRA Server for User Management - here's how we are Connecting JIRA to Crowd for our own Atlassian suite:
However, as per our resp. FAQ Will Identity Federation for AWS be available for Atlassian Crowd?, it is not available for Crowd itself :
The add-on could work within Crowd in principle, however Crowd currently lacks the Universal Plugin Manager (UPM) and support for publishing Crowd add-ons via the Atlassian Marketplace in turn.
Please watch/vote/comment on the following Crowd issue to raise Atlassian's priority for addressing this limitation:
AWS supports OpenID Connect (OIDC) and SAML 2.0 Identity Providers as detailed here. So your question is: "Can Crowd be a SAML 2.0 or OIDC IdP for AWS?". At the time of writing, the answer is no, but it could be done with a bit of coding:
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs