Crowd 1.3 Beta Release Notes

Older releases

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

20 February 2008

Crowd 1.3 will be launched early in March 2008. A beta release is currently undergoing internal testing. These release notes apply to Crowd 1.3 beta. We'll publish the final release notes with the release of Crowd 1.3.0.

If you would like to participate in testing the beta release, please contact Crowd Support.

Upgrading to Crowd 1.3 Beta

If upgrading from a previous version, please read the Upgrade Notes.

What's Coming in Crowd 1.3

 LDAP Authentication with Crowd Groups and Roles

  • Crowd 1.3 provides a new directory type, Delegated Authentication, combining the features of a Crowd internal directory with delegated LDAP authentication.
  • This allows you to have your users authenticated via an external LDAP directory while managing the groups and roles in Crowd.
  • Use Crowd's flexible and simple group management when the LDAP groups do not suit your requirements. For example, you can set up a group configuration in Crowd for use with Confluence and other Atlassian products.
  • Avoid the performance issues which might result from downloading large numbers of groups from LDAP.
  • Use the new Directory Importer, described below, to synchronize your LDAP users with your Crowd directory.
  • When a user logs in for the first time, Crowd automatically adds them to the Crowd directory if not already present.

 Cross-Directory User Importer

  • Our new Directory Importer allows you to copy your users from one directory into another.
  • Provided that the directory is defined in Crowd, you can copy from and to any directory type.
  • For example, you might import users, groups, roles and memberships from an LDAP directory to a new Delegated Authentication directory (described above) so that you can manage the users, groups and roles in Crowd while allowing users to log in with their LDAP passwords.
  • Read about the Directory Importer.

 Streamlined User Interface

  • The Crowd Administration Console has a new menu structure and an enhanced look-and-feel.
    sed functions, so that an administrator has fewer steps to perform and interaction is more intuitive.
  • The 'Help' links on the Administration Console point directly to the relevant documentation pages.

 Simplified Installation and Setup

  • Database configuration is now part of the Setup Wizard, which will update the configuration files based on the options you select.
  • You can choose between a JNDI datasource (i.e. server-managed) or a simpler JDBC configuration.
  • When upgrading, you can import an XML backup of your Crowd database or connect to an existing database via the Setup Wizard. This means that you don't have to go through the whole Setup Wizard, nor do a manual backup and restore of your Crowd database files.

 Logging and Profiling Configuration via Console

  • Enable profiling and configure your logging levels via the Crowd Administration Console.

 Improved Performance and Efficiency

  • You'll notice faster search results on the Administration Console screens, such as the Application Browser and User Browser, etc.
  • That annoying 'POSTDATA has expired' message no longer appears when you click the 'Back' button.
  • Search results returned to a Crowd application are now sorted alphabetically — such as the list of groups shown in a Confluence group picker.
  • We've fixed the Hibernate StaleStateException error that was causing occasional performance degradation and authentication failures.
  • You can choose to store the login session tokens in the Crowd database (as done prior to Crowd 1.3) or in memory (new option as from Crowd 1.3). Depending upon your installation, in-memory storage could greatly improve response times during authentication. Read about configuring token storage.
  • Gzip compression of Crowd Security Server output is now optional. You can turn it on or off via the Crowd Administration Console. Some reasons why you may want to turn Gzip compression off:
    • It may be easier to debug problems using uncompressed data.
    • Some agents, such as older versions of Internet Explorer, have problems with the Gzip format.

 Highlights for the Developers

  • The Java client library API has been upgraded. Read more about the API changes and the upgrade notes.
  • You can pass the file to a client application as an environment variable.

Updates and Fixes in this Release

key summary priority status

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

Last modified on May 26, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.