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

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

--On Friday, April 16, 2004 6:45 PM -0700 Quanah Gibson-Mount 
<quanah@stanford.edu> wrote:

Looking further into the code, I found the problem, and it is in our JNDI 
process.

The entry starts with:

> objectClass: inetOrgPerson
> objectClass: organizationalPerson
> objectClass: person
> objectClass: suCampusResident
> objectClass: suOperational
> objectClass: suPerson

and then our process does this:

>         replace\objectclass\"suPerson", "organizationalPerson",
> "inetOrgPerson", "person", "suOperational"

which means that the suCampusResident objectclass gets deleted, leading to 
the schema violation.

--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