LDAP provides you just Authentication/Authorization. Sometimes more. Atlassian Crowd offers Single Sign On. When you have multiple web apps, e.g. Confluence, Jira, Fisheye, etc you don't want to sign on to each one of them, if you're singed in on one.
Also Crowd offers OpenId, which means that you can use it with any app that supports OpenId. LDAP requires configuration of each application to the corresponding LDAP Server.
我们使用crowd的真正原因是为了进行多目录身份验证。我们的内部用户位于活动目录中。我们的客户可以通过人群进行身份验证，以通过一些自定义数据库魔法使用他们在我们的应用程序中使用的相同登录来访问 JIRA/Confluence，并且应用程序身份验证由人群在内部处理。与试图将所有内容都塞进 AD 相比，它确实让事情变得更加顺利。
The real reason we use crowd is for multiple directory authentication. We have our internal users in active directory. We have our customers that can authenticate through crowd to access JIRA/Confluence using the same sign on they use in our application through some custom database magic, and application authentication is handled internally by crowd. It's really just makes things so much smoother, than trying to cram everything into AD.
My reason for using Crowd is a little more selfish. I'm trying to lower the barriers to sell my group on using proper software development tools/procedures (development isn't our core function, but it is a very large part of what we do).
Since I'm trying to get buy-in on multiple systems (JIRA, Confluence, Jenkins) being able to manage accounts through a single interface is much easier to sell rather than having to get my manager (and other users that have historically been highly resistant to change) to create and maintain accounts in three different systems.
Crowd lets me do this in a (relatively) easy way.
Using Crowd this way also lets us create a 'guest' account that provides restricted access to our data if we do happen to need to make it visible to someone outside our group (like a stakeholder for example).
I just had this same question but ended up not installing Crowd. Directly from Atlassian's docs:
Connecting Confluence to JIRA for User Management
When to use this option: Choose this option as an alternative to Atlassian Crowd, for simple configurations with a limited number of users.
We use JIRA and FishEye+Crucible and have about 7 users overall but didn't see Crowd giving much benefit for that size installation, however both JIRA and FeCru are fantastic
发布评论
评论（4）
LDAP 只为您提供身份验证/授权。有时更多。
Atlassian Crowd 提供单点登录。当您拥有多个 Web 应用程序（例如 Confluence、Jira、Fisheye 等）时，如果您已登录其中一个应用程序，则您不想登录其中的每一个应用程序。
Crowd 还提供 OpenId，这意味着您可以将其与任何支持 OpenId 的应用程序一起使用。
LDAP 需要将每个应用程序配置到相应的 LDAP 服务器。
LDAP provides you just Authentication/Authorization. Sometimes more.
Atlassian Crowd offers Single Sign On. When you have multiple web apps, e.g. Confluence, Jira, Fisheye, etc you don't want to sign on to each one of them, if you're singed in on one.
Also Crowd offers OpenId, which means that you can use it with any app that supports OpenId.
LDAP requires configuration of each application to the corresponding LDAP Server.
我们使用crowd的真正原因是为了进行多目录身份验证。我们的内部用户位于活动目录中。我们的客户可以通过人群进行身份验证，以通过一些自定义数据库魔法使用他们在我们的应用程序中使用的相同登录来访问 JIRA/Confluence，并且应用程序身份验证由人群在内部处理。与试图将所有内容都塞进 AD 相比，它确实让事情变得更加顺利。
The real reason we use crowd is for multiple directory authentication. We have our internal users in active directory. We have our customers that can authenticate through crowd to access JIRA/Confluence using the same sign on they use in our application through some custom database magic, and application authentication is handled internally by crowd. It's really just makes things so much smoother, than trying to cram everything into AD.
我使用 Crowd 的原因有点自私。我正在努力降低向我的团队推销使用适当的软件开发工具/程序的障碍（开发不是我们的核心职能，但它是我们所做工作的很大一部分）。
由于我试图获得多个系统（JIRA、Confluence、Jenkins）的支持，因此能够通过单个界面管理帐户更容易销售，而不是必须让我的经理（以及历史上一直高度重视的其他用户）抵抗变化）在三个不同的系统中创建和维护帐户。
Crowd 让我以一种（相对）简单的方式做到这一点。
通过这种方式使用 Crowd 还可以让我们创建一个“访客”帐户，如果我们确实需要让我们的数据对我们组之外的人（例如利益相关者）可见，则该帐户可以提供对我们数据的受限访问。
My reason for using Crowd is a little more selfish. I'm trying to lower the barriers to sell my group on using proper software development tools/procedures (development isn't our core function, but it is a very large part of what we do).
Since I'm trying to get buy-in on multiple systems (JIRA, Confluence, Jenkins) being able to manage accounts through a single interface is much easier to sell rather than having to get my manager (and other users that have historically been highly resistant to change) to create and maintain accounts in three different systems.
Crowd lets me do this in a (relatively) easy way.
Using Crowd this way also lets us create a 'guest' account that provides restricted access to our data if we do happen to need to make it visible to someone outside our group (like a stakeholder for example).
我只是有同样的问题，但最终没有安装 Crowd。直接来自 Atlassian 文档：
我们使用 JIRA 和 FishEye+Crucible，总共有大约 7 个用户，但没有看到 Crowd 为这种规模的安装带来太多好处，但是 JIRA 和 FeCru 都很棒
I just had this same question but ended up not installing Crowd. Directly from Atlassian's docs:
We use JIRA and FishEye+Crucible and have about 7 users overall but didn't see Crowd giving much benefit for that size installation, however both JIRA and FeCru are fantastic