Re: Object Class Violation

Richard Bullington-McGuire wrote:
> 
> On Tue, 2 Aug 2005, Manuel Amador (Rudd-O) wrote:
> 
>> When the host attribute is added to the person structure, the object
>> class list is updated to include the problematic objectclass you
>> mentioned a few e-mails ago.  This was done by me like that because,
>> back in the golden days, that was the only way to add a host attribute
>> without disabling OC checking.
> 
> 
> When I started setting my LDAP schema up in OpenLDAP 2.0, I found I 
> needed to add a reference to the ldapns.schema file to my slapd.conf to 
> get things working.
> 
> This schema, by Luke Howard of PADL.com, did the trick:

Hi Richard,
  That schema is the same type of addition which I proposed earlier that 
we could deliver, but I didn't really like the idea because it was not 
transparent to the user.

  Finally, it seems that it is required. And then we can remove the 
account object class once and for all.

  We need a patch against the 1.7 svn branch, which:

	- queries the existence of 'hostObject' from the running server's schema

	- enables or greys out the associated dialog box "this user logs on 
from different hosts", based on if 'hostObject' exists or not

	- replaces 'account' with 'hostObject'


  This is not a huge task. Any volunteers? This patch would take 
precedence over the 3 or 4 other patches which are to be reviewed now.


BR,
Mike