This page last changed on Sep 03, 2007 by justen.stepka@atlassian.com.

The Crowd development team has released Crowd 1.1.2.

Crowd 1.1.2 is a recommended upgrade from Crowd 1.1.1 since it provides improved integration with JIRA and Confluence, and tidier functionality for multiple directories.

For cross product compatibility, you must upgrade to the following versions of each product:

  • Crowd 1.1.2 or later
  • Bamboo 1.2.2 or later
  • Confluence 2.5.6 or later
  • JIRA 3.7.4 or later

Integration with JIRA user management

With Crowd 1.1.2, you can now turn external user management off in JIRA. This means that you can allow signup via JIRA, and you can manage your users within JIRA. Changes will flow through to Crowd.

JIRA has an automatic group membership feature. This means that any new user added through JIRA will automatically be a member of all groups which have the JIRA Users permission. In this way, you can ensure that a new user is automatically added to several groups when they sign up with JIRA.

RSS feeds

Crowd 1.1.2 fixes the problem experienced accessing RSS feeds from JIRA including retrieving JIRA issues via Confluence macros (e.g. the JIRA portlet macro).

Improved LDAP Performance

Crowd 1.1.2 now queries LDAP repositories in a more efficient manner that will give a dramatic performance increase for those with large numbers of LDAP groups.

Other Fixes in Crowd 1.1.1

Errors were reported by the JIRA trusted connection.

  • APP_UNKNOWN; Unknown Application: {0}; ["confluence:4557196"]
JIRA Issues (23 issues)
Key Summary Priority Status
CWD-314 Not able to Retrieve Issues (RSS) if JIRA is Integrated with Crowd Blocker Resolved
CWD-297 JIRA performance improvements Blocker Resolved
CWD-472 OpenID not working with LiveJournal Critical Resolved
CWD-540 CrowdID Install Documentation Mistake Major Resolved
CWD-503 Cannot modify user profile when using Crowd authentication, fails with NullPointer on RemotePrincipal.getEmail() Major Resolved
CWD-497 Crowd integration of Extranet JIRA has authentication problems Major Resolved
CWD-496 requiresPasswordChange gets reset to false during login for an InternalDirectory Major Resolved
CWD-495 Principals are being added with whitepace in their usernames Major Resolved
CWD-492 Concurrent modification exception in JIRAAuthenticator logout code Major Resolved
CWD-487 The upgrade manager should run after setup is complete Major Resolved
CWD-484 When Confluence 2.6 releases we need to move the code from the bamboo-intergration module back into the atlassian-user module. Major Resolved
CWD-478 Update Confluence Integration Doc Major Resolved
CWD-462 Implement add user method of OSUser for JIRA Major Resolved
CWD-452 JIRA user management should allow admins to update Crowd users Major Resolved
CWD-448 Remote application's calls to removePrincipal(name) only removes the first principal it finds Major Resolved
CWD-447 Remote application's calls to removeRole(name) only removes the first role it finds Major Resolved
CWD-446 Remote application's calls to removeGroup(name) only removes the first group it finds Major Resolved
CWD-421 Client JARs in client/lib are incomplete Major Resolved
CWD-394 Full Name Search always returns all users Major Closed
CWD-132 Windows service registration feature. Major Resolved
CWD-420 Configuring multiple repositories may result in duplicate users Minor Resolved
CWD-390 Browser cookies cause NullPointerException when integrated with Confluence Minor Resolved
CWD-383 misspelling in wsdl - encryptedCrednetial Minor Resolved

Cheers,

The Atlassian Crowd Development Team

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