RE: Rejected update for an attribute that wasn't being updated?

[Quanah Gibson-Mount <quanah@stanford.edu>]

--On Friday, April 16, 2004 8:45 PM -0700 Howard Chu <hyc@highlandsun.com> 
wrote:

> > The *unmodified* entry contains the above attributes.  As I
> > noted before,
> > all that the objectClass "suCampusResident" requires is
> > suResidenceRequiredAttribute.  That is present in the entry
> > (see above).
> >
> > Also, we *always* have schema checking on (it has been in our
> > slapd.conf
> > since the day we deployed OpenLDAP into production).
> >
> > I'll also note that the entry was *successfully* modified on
> > 1/11/2004, and
> > created 05/16/2003.  So what you are saying doesn't make any sense.
>
> Has your schema been changed in that period of time?
>
> What "suCampusResident" *requires* is irrelevant in this case. The server
> complains that "suResidenceTSO" is *not allowed* - so, which objectclass
> in this particular entry has a MAY for the suResidenceTSO attribute?

objectclass ( 1.3.6.1.4.1.299.11.3.110 NAME 'suCampusResident'
       DESC 'Stanford University On Campus Resident'
       AUXILIARY
       MUST ( suResidenceRequiredAttribute )
       MAY ( suResidenceCode $ suResidenceName $ suResidenceRoom $ 
suResidencePhone $ suResidenceTSO )

The only change the schema has had since the last time I loaded this LDIF 
file into the test directories was to add the "suSearchID" attribute, which 
(a) isn't populated currently, (b) is a MAY, and (c) isn't a part of the 
suCampusResident objectclass.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/TSS/Computing Systems
ITSS/TSS/Infrastructure Operations
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html