Environment
Novell iManager 2.7
Situation
Trying to LUM enable a user in iManager returns a -609 error.
The console utility namuseradd works properly.
Resolution
If a mandatory attribute for the posixAccount class is also an optional attribute for another class it causes iManager to fail.
In one case the homeDirectory attribute was an optional attribute for Organizational Person as well as a mandatory attribute for posixAccount.
In another case both uidNumber and gidNumber attributes were in the optional list for the Person class.
In one case the homeDirectory attribute was an optional attribute for Organizational Person as well as a mandatory attribute for posixAccount.
In another case both uidNumber and gidNumber attributes were in the optional list for the Person class.
Technically it should not matter if class attribute assignments overlap but it will cause the LUM enable task in iManager to fail.
Make sure that none of the mandatory attributes for posixAccount are optional attributes for any other class.
See KB 7008201 - "Modifying eDirectory Schema using LDIF files" for details on how to remove the problem attributes from a class definition. Note that you should NOT attempt to remove uniqueID from any base class definition. The LUM plugin should handle that particular case already.
See KB 7008201 - "Modifying eDirectory Schema using LDIF files" for details on how to remove the problem attributes from a class definition. Note that you should NOT attempt to remove uniqueID from any base class definition. The LUM plugin should handle that particular case already.
Additional Information
Fixed in iManager 2.7.4 patch 3 or later.