When attempting to create a user in Identity Manager, you encounter LDAP: error code 65 - Object Class Violation. This error typically occurs when the user object requires custom object classes that are not properly defined in the Identity Manager schema, even when all required attributes are provided in the UI.
Identity Manager 14.5
This error indicates a mismatch between the schema definition in the Identity Manager Management Console and the requirements of the underlying LDAP directory. The ImsManagedObject definition for the 'User' object within the Directory.xml file lacks the necessary custom object classes, causing the directory to reject the creation request as an object class violation.
To resolve this violation, you must update the Identity Manager schema definition and migrate existing user data to include the required object classes.
Phase 1: Update Identity Manager Schema
Directory.xml file for the Corporate User Store.ImsManagedObject line for the User: <ImsManagedObject name="User" objectclass="top,imUser" ...>objectclass attribute (e.g., objectclass="top,imUser,imUserAux").Phase 2: Migrate User Store Data You must update existing user entries in your LDAP directory to reflect the new schema requirements.
objectClass: imUserAux to each user entry).Note: For Virtual Appliance (vApp) environments, use the dxdumpdb and dxloaddb commands to perform these operations.