Crowd 1.6 Release Notes

18 December 2008

The Atlassian Crowd team is proud to present Crowd 1.6.

Crowd 1.6 introduces a new, more intelligent caching system that will improve performance of Crowd with LDAP, particularly for large and off-site directories.

This release also brings a quicker setup process for Atlassian applications. The Crowd Administration Console allows you to choose the application you want to integrate (JIRA, Confluence, Bamboo, FishEye or Crucible), prompts you for the necessary information and automatically adds the required directory and groups.

There are new directory connectors for OpenDS, Fedora Directory Server and OpenLDAP (based on the Posix/NIS schema).

You'll find a number of smaller improvements in this release too. More unusual characters are supported in the UI and in LDAP directories. Using Crowd's new authentication-related API events, you can create plugins that react when a user logs in, logs out, changes their password, and so on.

Highlights of this release:

Responding to your feedback:
(green star) 38 votes satisfied
Keep logging your votes and issues. They help us decide what needs doing!

Upgrading to Crowd 1.6

You can download Crowd from the Atlassian website. If upgrading from a previous version, please read the Crowd 1.6 Upgrade Notes.

Highlights of Crowd 1.6

Smarter Caching

Crowd 1.6 introduces a new, more intelligent caching system that will improve performance of Crowd with Microsoft Active Directory and ApacheDS. You should notice the improvement particularly in directories which are large, slow or off site.

  • Crowd now keeps an up-to-date cache of user, group and role information retrieved from the LDAP directory.
  • The cache uses lazy loading where possible, storing only the information that is required rather than loading the entire directory into the cache.
  • Crowd ensures that the cache remains up to date by monitoring the LDAP directory for updates. When a change occurs, Crowd updates the server-side cache incrementally.
  • Refer to our documentation for an overview of Crowd caching and details of the LDAP caching.

Quick Application Setup

Crowd 1.6 brings a quicker setup process for Atlassian applications. Crowd now supports specific application types for JIRA, Confluence, Bamboo, FishEye and Crucible.

  • The Crowd Administration Console allows you to choose the type of application you want to integrate and prompts you for the necessary information.
  • Crowd automatically adds the required directory and groups. For example, if you are integrating Crowd with JIRA, Crowd will add the 'jira-users', 'jira-developers' and 'jira-administrators' groups for you.
  • The setup process will prompt you to import the users from JIRA or the relevant application.
  • Then you can move quickly to the next stage, configuring the application's libraries and other settings, which is still a manual process.

 

Connectors for OpenDS, Fedora DS and OpenLDAP (Posix)

Crowd 1.6 provides three new built-in directory connectors. The new connectors do not affect any directories already configured. They will make it easier to set up your directory if you are starting from scratch.

Spring Security 2

Other Good Things

  • In Crowd 1.5, we introduced an early version of the Atlassian Plugin Framework 2. Crowd 1.6 now supports version 2.1 of the Atlassian Plugin Framework.
  • Crowd now fires a number of API events related to authentication and change of password. This allows developers to create listener plugins that spring into action when a user logs in, logs out, changes their password, and so on.

Complete List of Improvements and Fixes

key summary priority status

Unable to locate JIRA server for this macro. It may be due to Application Link configuration.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport