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 authorised Crowd user to update their own user profile and password and to view their authorisation 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 customised event listeners and password encoders.
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.
For our development community, the new plugin framework supports customised 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.
4 new feature requests implemented
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.
Add Comment