Crowd 2.4 : Crowd 1.4.1 Release Notes

23 May 2008
The Atlassian Crowd team is delighted to present Crowd 1.4.1. This release includes a few bug fixes and a new feature — trusted proxy servers.

If you are running applications behind one or more proxy servers, you may find it useful to configure Crowd to trust the proxies' IP addresses. When a proxy server forwards an HTTP request, Crowd will recognise the request as coming from the request's originator, not the proxy server. This is particularly useful if you want single sign-on amongst several applications running behind different proxy servers. Our documentation tells you how to set this up.

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.1

JIRA Issues (7 issues)
Key Summary Priority Status
CWD-1063 Under heavy load client libraries will leak sockets into CLOSE_WAIT. Critical Resolved
CWD-1061 crowd-integration-client-1.4 does not work with Jive in a clustered environment, because the CrowdUser object contains a non-serializable member field (securityServerClient). Major Resolved
CWD-1051 Confluence error: Illegal configuration. No default cache is configured Major Resolved
CWD-1049 The 'crowd' context is hardcoded into the login.jsp page Minor Resolved
CWD-1046 Profiling (under Admin -> Logging & Profiling) is not working Major Resolved
CWD-541 Allow specification of Trusted Proxy Servers Critical Resolved
CWD-183 Problems with LDAP group or user names that contain / or \. Major Resolved

Attachments: