We manage our eDir objects via LDAP using an in-house C program.

All was working fine until recently there was a request to populate the
employeeType attribute for users.

The documentation states that employeeType is a case ignore string, so
should accept any string value.
Populating employeeType via iManager works fine.

However when Itrying to populate the employeeType attribute from the C
program (using the exact same code as for other case ignore string
attributes), eDir returns error: Object class violation (65).
When removing employeeType from the update code, all works fine again
for the rest of the attributes.

Any idea why this would happen?

hscheff's Profile: https://forums.netiq.com/member.php?userid=7118
View this thread: https://forums.netiq.com/showthread.php?t=53528