This page last changed on Jun 30, 2008 by smaddox.

1 July 2008
The Atlassian Crowd team is delighted to present Crowd 1.4.4.

You can now enable or disable support for nested groups on each LDAP user directory. If you upgrade your Crowd installation with existing LDAP directory connectors, nested group support will remain enabled for those directories. To configure nested group support for new or existing LDAP connectors, go to the connector configuration screen in your Administration Console.

When using Crowd for single sign-on (SSO), you can now specify the SSO cookie name for each application. Under the standard configuration, Crowd will use a single, default cookie name for all Crowd-connected applications. For more information, read about the crowd.properties file.

Don't have Crowd 1.4 yet?
Take a look at the new features and other highlights in the Crowd 1.4 Release Notes.

Complete List of Fixes in Crowd 1.4.4

JIRA Issues (15 issues)
Key Summary Priority Status
CWD-1111 JIRA Performance with Crowd 1.4.3 and AD is very slow Blocker Resolved
CWD-1125 The directoryID is not populated on principals added automatically after authentication with a delegated directory Critical Resolved
CWD-125 Provide Lotus Domino Support Critical Resolved
CWD-1175 Please add a note about this bug on our import docs Major Closed
CWD-1169 Add note to Crowd-Bamboo integration docs on configuring explicit cache to bypass CWD-1167 Major Closed
CWD-1128 DelegatedAuthenticationDirectory.authenticate returns an LDAP-backed principal Major Resolved
CWD-1127 Enable the ability to configure nested group support for a given directory Major Resolved
CWD-1121 CrowdUserDetailsServiceImpl.generateAuthoritiesFromGroupNames throws a NullPointer if no groups are associated Major Resolved
CWD-1115 Per-application cookies. Major Resolved
CWD-1112 Checking if a user is a member of a group on large user ldap directories is slow and casuses OutOfMemoryException -- FAIL Major Resolved
CWD-1074 AD directory connector should check "Use Node Referrals" as the default Major Resolved
CWD-1059 Admin Cookie name should be different to application/user cookie name Major Resolved
CWD-690 Add setenv.sh file in the apache-tomcat-5.5.20/bin directory for easier memory management. Major Resolved
CWD-1167 If crowd-ehcache.xml is misconfigured, Bamboo Crowd Integration Client uses wrong default cache Minor Resolved
CWD-894 Dont hard code SSO cookie name Minor Resolved

Document generated by Confluence on Jul 30, 2009 01:30