Atlassian Crowd Review

LDAP connection is a valuable feature but exporting users/groups toward LDAP has room for improvement


What is most valuable?

User/groups assignment to applications, LDAP connection and the Apache module.

How has it helped my organization?

I setup and administrate Crowd for a client of ours. Users are able to perform Single Sign On on all the Atlassian products including Subversion authentication through an Apache module and soon GIT.

What needs improvement?

Exporting users/group toward LDAP and retrieving LDAP attributes like photo profile.

For how long have I used the solution?

2 years

What was my experience with deployment of the solution?

I haven't encountered any issues.

How are customer service and technical support?

Customer Service: On a scale from 1-5 I would give it a 5.Technical Support: On a scale from 1-5 I would give it a 5.

Which solution did I use previously and why did I switch?

No, it was a need since we use other Atlassian products.

How was the initial setup?

It is straightforward, especially because the standalone version requires only a few things to be configured.

What about the implementation team?

In-house, I perform setup and maintenance (security patches) on my own.

What's my experience with pricing, setup cost, and licensing?

$1,200 per year. Once setup, the management is really easy.

Which other solutions did I evaluate?

No, we didn't. I am currently evaluating other products to avoid possible vendor lock in and to explore possible new features.

What other advice do I have?

If your budget allows, it is worth purchasing Crowd once you have at least 2 Atlassian products like Jira and Confluence. I would start to put users in an LDAP directory, so other application that cannot connect to Crowd at least can connect to LDAP (see my article on http://opensource.com/business/14/5/top-4-open-source-ldap-implementations).
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest