Crowd 2.10.1 Release Notes

13 September 2016

Thank you for your feedback:

(green star) 83 votes satisfied

(green star) 3 feature and improvement requests fulfilled

Highlights of this release:


Faster than ever

We've improved how Crowd performs with aliases and applications with many directories without aggregated memberships.  

  See an example...

One of the configurations we tested with was an application with disabled membership aggregation and the following directory configuration:

  • 2 directories - one internal and one database cached LDAP directory
  • 2402 users in 401 groups in the internal directory (1 default group and 200 parent groups each with 1 child group)
  • 4000 users in 401 groups in the database cached LDAP directory
  • 2400 shadowing users

In this example, it took approximately 26 seconds to return all groups with their users (via /rest/usermanagement/1/group/membership), as opposed to approximately 30 minutes prior to this change.

We think you'll notice a significant difference in your Crowd instance.

Improved group membership synchronization behavior

We've added a new option that synchronizes group memberships for users who have been created in an LDAP directory, but have not yet been synchronised to Crowd. This gives you convenience, without sacrificing performance. 

Improved UI for LDAP configuration testing

We've improved the look and usability of LDAP configuration testing to ensure better experience when verifying your connection parameters and filters.

Complete list of improvements and fixes

Key Summary P Status
CWD-2650 Crowd doesn't create new users automatically in other directories when he first login, but after sometime Medium Closed
CWD-4344 Significantly Slower Sync to Confluence or JIRA in Crowd 2.8 due to /rest/usermanagement/1/group/membership High Closed
CWD-4197 Improve authentication performance when copying groups on login Medium Closed
CWD-3255 Incremental sync fails after authentication if default groups have been added to a remote Crowd directory or the user has been synced via authentication Medium Closed
CWD-3809 ApplicationServiceGeneric#searchNestedGroupRelationships performs n+1 queries in order to shadow users Medium Closed
CWD-3906 Performance drop considerably when Alias is enabled Low Resolved
CWD-4648 Local Crowd admin account is unable to login to Crowd when LDAP directory is locked out Low Resolved
CWD-4790 CVE-2016-6496: LDAP Java Object Injection in Crowd Highest Closed
CWD-1375 Add Application Wizard should prompt users to configure the application after completing the wizard Medium Resolved
CWD-1085 trailing spaces at crowd.home breaks installation Medium Closed
CWD-4689 Improve isCanonical check in InMemoryNonAggregatingSearchStrategy Medium Closed
CWD-4633 password plain-text in crowd external database setup Medium Closed
CWD-4388 Directory Type is blank for Connector directories Low Resolved
CWD-4369 When adding an application, "Select..." can be added as a group Low Resolved
CWD-4577 Default form action when adding user attribute is to update existing attributes Low Resolved
CWD-4489 Disable Quartz Phone Home Low Resolved
CWD-4482 UserDao.removeAttribute does not keep InternalUser.attributes property up to date Low Closed
CWD-4470 Getting direct users/groups doesn't return 404 for invalid group/user Low Closed
CWD-4740 Clarify the interaction of events and database transactions Low Closed
CWD-4695 Configure Tomcat to use relative URLs in redirections Low Resolved
CWD-4691 Clicking 'Revert to defaults' on the 'Logging & profiling' screen stops logging to logfile Low Closed
CWD-4673 When Internal Server error is thrown in Crowd console there should be a nice page with description what happened Low Closed
CWD-4730 Prevent race condition between user data synchronisation and user data updates Low Resolved

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport