-
Bug
-
Resolution: Fixed
-
Medium
-
1.6.1
-
None
-
None
-
4
-
For groups that contain over 1500 members AD returns the members in an attribute named member;range=0-1499, expecting the receiving application (Crowd) to do paging on the attribute values. Crowd does not recognize this attribute name, as it is expecting to find attributes called member. Because of this, group memberships cannot be resolved from the group side for large groups. The workaround for this issue is to use the Use the User Membership Attribute option.
The following are the consequences:
1-) To be able to use Crowd caching, the Use the User Membership Attribute must be enabled.
2-) Currently the LDAP caching supports groups with a maximum of 1499 users memberships.
The workarounds would be to:
1-) Disable caching (if using this workaround, to avoid performance issues, be sure the application side cache will timeout during out of peak hours or our of working hours).
2-) Create many directories and using filters, make sure they will have less than 1499 users each. This would allow to continue using LDAP caching.
[CWD-1445] Support *range* attribute for Active Directory
| Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1510155 ] | New: JAC Bug Workflow v3 [ 3365516 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Simplified Crowd Development Workflow v2 [ 1392988 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1510155 ] |
| Workflow | Original: Crowd Development Workflow v2 [ 272247 ] | New: Simplified Crowd Development Workflow v2 [ 1392988 ] |
| Workflow | Original: JIRA Bug Workflow v2 [ 173558 ] | New: Crowd Development Workflow v2 [ 272247 ] |
| Assignee | Original: David O'Flynn [Atlassian] [ doflynn ] | New: Peggy [ pkuo ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Support Count Updater
made changes -
| Support reference count | Original: 3 | New: 4 |
David O'Flynn [Atlassian]
made changes -
| Fix Version/s | New: 2.0.1 [ 14670 ] | |
| Fix Version/s | Original: 2.0 [ 12269 ] | |
| Fix Version/s | Original: Sprint 4 [ 14663 ] |
David O'Flynn [Atlassian]
made changes -
| Fix Version/s | New: 2.0 [ 12269 ] | |
| Fix Version/s | New: Sprint 4 [ 14663 ] |
Support Count Updater
made changes -
| Support reference count | New: 3 |
| Description |
Original:
For groups that contain over 1500 members AD returns the members in an attribute named member;range=0-1499, expecting the receiving application (Crowd) to do paging on the attribute values. Crowd does not recognize this attribute name, as it is expecting to find attributes called member. Because of this, group memberships cannot be resolved from the group side for large groups. The workaround for this issue is to use the Use the User Membership Attribute option.
The following are the consequences: 1-) To be able to use Crowd caching, the *Use the User Membership Attribute* must be enabled. 2-) Currently the LDAP caching supports a maximum of 1499 users. The workarounds would be to: 1-) Disable caching 2-) Create many directories and using filters, make sure they will have less than 1499 users each. This would allow to continue using LDAP caching. |
New:
For groups that contain over 1500 members AD returns the members in an attribute named *member;range=0-1499*, expecting the receiving application (Crowd) to do paging on the attribute values. Crowd does not recognize this attribute name, as it is expecting to find attributes called member. Because of this, group memberships cannot be resolved from the group side for large groups. The workaround for this issue is to use the Use the User Membership Attribute option.
The following are the consequences: 1-) To be able to use Crowd caching, the *Use the User Membership Attribute* must be enabled. 2-) Currently the LDAP caching supports groups with a maximum of 1499 users memberships. The workarounds would be to: 1-) Disable caching (if using this workaround, to avoid performance issues, be sure the application side cache will timeout during out of peak hours or our of working hours). 2-) Create many directories and using filters, make sure they will have less than 1499 users each. This would allow to continue using LDAP caching. |