-
Suggestion
-
Resolution: Low Engagement
-
None
-
1
-
Steps to Reproduce
- Create a custom object class in LDAP, (tested this with Apache DS) set the object's parents to the default organizationalPerson (for Apache DS, exactly the same as inetOrgPerson's parent):
- Create a user entity that uses this custom object class instead of the default inetOrgPerson
- Modify the LDAP connector in Crowd, and set the User Object Class to this new custom object class, and set the user object filter to (objectClass=connieuser2) . Set the Modify User Attributes and the Modify User permissions.
- Sync the directory, notice that the user is synced correctly.
- Try to modify the user's Firstname, Lastname, or the Email Address. Notice that the UI shows Update Successful, but the changes are reverted (unable to modify those attributes). (see: https://jira.atlassian.com/browse/CWD-2888) . Note however, that password changes are reflected correctly in the LDAP server. Only the firstname, lastname and email address change is ignored.
[CWD-2892] Full Support for Custom LDAP Object Classes
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Labels | New: cleanup-seos-fy25 |
Support reference count | New: 1 |
Workflow | Original: JAC Suggestion Workflow [ 3388935 ] | New: JAC Suggestion Workflow 3 [ 3629716 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1389956 ] | New: JAC Suggestion Workflow [ 3388935 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Status | Original: Needs Verification [ 10004 ] | New: Gathering Interest [ 11772 ] |
Epic Link | Original: CWD-4705 [ 600142 ] |
Status | Original: Open [ 1 ] | New: Needs Verification [ 10004 ] |
Epic Link | New: CWD-4705 [ 600142 ] |
Workflow | Original: Crowd Development Workflow v2 [ 399885 ] | New: Simplified Crowd Development Workflow v2 [ 1389956 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 98130 ] |