Crowd 1.4 Release Notes

Older releases

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

8 May 2008

The Atlassian Crowd team is proud to release Crowd 1.4.

Crowd 1.4 supports nested groups in LDAP directories. This means a group can now be a member of another group, making management of permissions much easier. For example, a Crowd-integrated Confluence or JIRA site will see users in sub-groups as members of the parent group.

The new Self-Service Console gives you the option to allow any authorized Crowd user to update their own user profile and password and to view their authorization details.

There's a new directory connector for Novell eDirectory. Crowd also supports read-only connections to an LDAP directory using the Posix schema. This is useful if you have a Unix installation and want to integrate it with an LDAP directory.

For the development community, a new plugin framework supports customized event listeners and password encoders.


Highlights of this release:


Responding to your feedback:
(green star) 4 new feature requests implemented
(green star) 90 votes satisfied

Keep logging your votes and issues. They help us decide what needs doing!


Upgrading to Crowd 1.4

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

Highlights of Crowd 1.4

Nested Groups

  • In your LDAP directory, you can assign a group as a member of another group.
  • In Crowd, you can map any group to an application, including a group which contains other groups. Currently, nested groups are supported for LDAP directory connectors only.
  • For example, you might have two LDAP groups: 'engineering-group' and 'payroll-group'. Now you want to allow all members of those groups to access your Confluence wiki. You can create a group called 'confluence-users', mapped to the Confluence application, with members 'engineering-group', 'payroll-group' and any other groups and users. Crowd will allow members of those groups and sub-groups to log in to Confluence. When Confluence requests a list of the users in the 'confluence-users' group, Crowd will present all users in the group plus all users in its sub-groups.
  • Good news for our Confluence, JIRA and other Atlassian customers — this feature satisfies your requests for nested groups in those products too.
  • Take a look at our documentation.

Self-Service Console

  • Crowd users, including non-administrators, can log in to Crowd.
  • Change or reset your own password.
  • Update your user profile.
  • View your group and role membership.
  • See a list of the applications you can log in to.
  • The new User Guide explains the ins and outs.

Novell eDirectory Connector

Posix Support for LDAP Directories

  • Crowd supports read-only connections to an LDAP directory using the Posix/NIS schema.
  • Initially, our support is targeted at OpenLDAP directories.
  • This is useful if you have a Unix installation and want to integrate with an LDAP directory.
  • Here's our documentation on connecting your LDAP directory using the Posix/NIS schema.

Plugin Framework

  • For our development community, the new plugin framework supports customized event listeners and password encoders.
  • For example, you might decide to write your own event listener to audit failed Crowd authentication requests. Within Crowd itself, the reset password listener uses the new event framework.
  • You can create your own plugin to use a specific password encryption algorithm that Crowd does not support out of the box. Crowd's own password encoders provide examples of such plugins.

More than 30 Improvements and Bug-Fixes

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?

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