-
Bug
-
Resolution: Fixed
-
Low
-
2.5.3
-
None
-
App server: Tomcat application server 5.5.15
JDK: Sun 1.5.0_10
LDAP server: SunOne Directory server 5.2
OS: Redhat Enterprise Server 3
Use Case: Administration : Manage Groups : Browse Pagination
Issues:
- LDAP queries select every group name for each page load (potentially thousands)
- Pagination does not adequately support thousands of groups
Suggestions:
- Cache LDAP group names
- Improve pagination to support thousands of groups
- Implement search within a result set
- Separate LDAP & Local groups
- Configuration option to hide Manage Groups function for LDAP groups
ldap query filters noted on this page:
filter="(&(objectClass=brownGroup)(objectClass=brownGroup))" attrs="brownGroupRDN
filter="(&(objectClass=brownGroup)(objectClass=brownGroup))" attrs="brownGroupRDN
[2 queries returning all group names for each page...no caching, and no limiting record set returned]
- is related to
-
CONFSERVER-13972 Navigation bar for "Manage Groups" does not show all pages.
- Closed
- relates to
-
CONFSERVER-12319 Adding users to a large group is slow with default (Hibernate) user management
-
- Closed
-
The performance of external user management is dramatically improved in Confluence 3.5. LDAP data is synchronised locally in most configurations, so you should no longer see this issue in Confluence.
Further, permission checking is improved for instances with large groups. The caching of memberships has now been optimised for the most frequent permission check queries which are done on the user management system. You should see a marked improvement here for large instances that use internal user management too.
More information about the Confluence 3.5 release is available here: Confluence 3.5 Release Notes.