Crowd - An extension to Active Directory
November 14, 2017
Crowd - An extension to Active Directory
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Atlassian Crowd
Atlassian Crowd is currently being utilized as a Single Sign-On for departments that utilize the other Atlassian software applications including JIRA, Confluence, HipChat and Core.
We use it as an extension to our existing sign-on directories including Active Directory as well as our other systems and utilities. We use it to help unify credentials to ensure everyone can access the systems they need using one alias.
We use it as an extension to our existing sign-on directories including Active Directory as well as our other systems and utilities. We use it to help unify credentials to ensure everyone can access the systems they need using one alias.
- The ability to Govern Group Permissions for synchronizing users into Crowd, keeping only the users you want in Crowd and keeping unwanted access out. Ability to define authentication permissions and having automated group definitions for new users.
- Integration into our existing systems, as it becomes merely an extension rather than a separate entity. It works seamlessly with almost all of our systems.
- Always up to date with compliance and security requirements of the organization. The ability to audit is very key. It's surprising how many systems don't have a fully supportive auditing system.
- Some systems that are not crucial turned into more work than what was originally deemed necessary to successfully deploy Crowd.
- Linux support was there as it was built mostly to support Windows based systems
- Documentation was supported but most issues we had required us to contact Atlassian support.
- New systems are tough when it comes to an ROI, as a dollar amount for saving time on a sign-in can be tough to track. Like most new systems that makes things slightly easier to execute as an end user or manage or support, it really might come down to the existing structure of how a company manages its users.
- The positives are always with the end user, which I have to say, Crowd was able to accomplish.
In most ways, I preferred Duo Security as it offered a better 2-factor authentication method, and Crowd is definitely better than just having to rely on Active Directory.
I have always been of the mind to have a centralized server that sits between your active directory (azure or on premise) and the systems that you integrate it with via LDAP or similar protocols.
It would surprise a lot of people to see how many organizations do not secure their active directory or LDAP connections.
I have always been of the mind to have a centralized server that sits between your active directory (azure or on premise) and the systems that you integrate it with via LDAP or similar protocols.
It would surprise a lot of people to see how many organizations do not secure their active directory or LDAP connections.