Full Support for Custom LDAP Object Classes

Steps to Reproduce

1. 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):
   
2. Create a user entity that uses this custom object class instead of the default inetOrgPerson
3. 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.
4. Sync the directory, notice that the user is synced correctly.
5. 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.