Crowd 1.5 Release Notes
4 September 2008The Atlassian Crowd team is proud to present Crowd 1.5.
Crowd now supports single sign-on (SSO) to Google Apps. Do you use Google Apps for your office documentation, calendar and collaboration tools? Using Crowd's SSO, your users can log in once then move seamlessly between Google Apps and other Crowd-integrated applications like JIRA, Confluence, Jive Forums and others.
Crowd 1.5 has a new directory connector, supporting read-only connections to Apple's OS X Open Directory server.
Developers will be interested in Atlassian's new Plugin Framework, now supported in Crowd 1.5. The new Google Apps connector, implemented as a plugin, provides a useful example for developers wanting to extend Crowd's functionality by building a Crowd plugin.
This release brings many improvements and fixes, including much faster user imports and database imports, JNDI mail configuration and a cleaner upgrade process.
Highlights of this release:
Responding to your feedback:
45 votes satisfied
Keep logging your votes and issues. They help us decide what needs doing!
Upgrading to Crowd 1.5
Highlights of Crowd 1.5
Single Sign-On to Google Apps
- Crowd now supports single sign-on (SSO) to Google Apps.
- Users can log in to Google Apps using their corporate username and password.
- An example of Google Apps SSO in action: A user clicks through from a link in a JIRA issue. The document opens directly in Google Apps. No need to log in again, no need to remember a different password.
- Administrators can use Crowd's groups to authorize access to Google Apps.
- Enjoy the security and convenience of managing all your users in one place.
- Set up Google Apps SSO in two easy steps: Generate the keys in Crowd then enter the information in Google Apps.
Plugin Framework 2.0 and API
- Crowd 1.5 comes with Atlassian's new Plugin Framework, based on Spring Dynamic Modules using an embedded OSGi container.
- The new Google Apps connector is implemented as a plugin, using the new Plugin Framework. This provides a useful example for developers wanting to extend Crowd's functionality by building a Crowd plugin.
- The Plugin Framework is experimental at this stage. We'd be delighted to have your feedback via our JIRA project.
- Crowd now fires an API event when a create/update/delete operation is performed at directory level. Developers can create listener plugins which spring into action when a specific event occurs. For example, the plugin might do something when a user is created, or when a group is deleted, and so on.
Other Improvements and Bug-Fixes
- When configuring your mail server, you can now choose between SMTP and a JNDI location. This allows you to use an SSL connection to your mail server.
- Importing users into a Crowd directory from Atlassian applications or a CSV file is now much faster when dealing with large user bases.
- Importing Crowd data from an XML backup is also much faster, due to the use of JDBC batching.
- CrowdID has been updated to the latest OpenID 2.0 specification. CrowdID, shipped with Crowd, allows your corporation to act as an OpenID provider for your employees.
- We have moved the
crowd.propertiesfile for the Crowd Administration Console to the Crowd Home directory, so that upgrading Crowd will be cleaner and easier from now on.
- Crowd will respond to a 'require password change' attribute and force the user to change their password before logging in.
Complete List of Improvements and Fixes