FW: Windows build works only as read-only (ITS#2349)

[hyc@highlandsun.com]

Forwarding a copy for record-keeping sake.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

-----Original Message-----
From: Tracy Boehrer [mailto:tboehrer@calltower.com]
Sent: Friday, March 07, 2003 7:35 AM
To: Howard Chu
Subject: RE: Windows build works only as read-only (ITS#2349)


Thank you... our replies passed each other in the ether...

-----Original Message-----
From: Howard Chu [mailto:hyc@highlandsun.com]
Sent: Friday, March 07, 2003 9:34 AM
To: Tracy Boehrer
Subject: RE: Windows build works only as read-only (ITS#2349)


Please re-read the message I sent you before, which you included below:

"Whatever attribute appears as the left-most RDN of your DN
must be present in the body of the entry."

If your DN is "cn=gringo,dc=calltower,dc=com"
then "cn=gringo" MUST appear in the entry.

I don't know how to state this any more plainly. Go and read the original
X.500 document, defining the X.500 information model, if you need more
details on this requirement.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: Tracy Boehrer [mailto:tboehrer@calltower.com]
> Sent: Friday, March 07, 2003 7:21 AM
> To: Howard Chu
> Subject: RE: Windows build works only as read-only (ITS#2349)
>
>
> If I reduce the LDIF I sent to:
>
> 	dn: dc=calltower,dc=com
> 	objectClass: dcObject
> 	objectClass: organization
> 	dc: calltower
> 	o: CallTower
> 	description: CallTower
>
> it works.  However, if I add the next two lines:
>
> 	dn: cn=gringo,dc=calltower,dc=com
> 	objectClass: ldapSubentry
>
> it produces the error.  However, if you look at the
> definition for "ldapSubentry", "cn" is defined as "MAY".  So
> I am at a loss as to where the schema is requiring "cn"?  Am
> I just misunderstanding something else?
>
>
> -----Original Message-----
> From: Howard Chu [mailto:hyc@highlandsun.com]
> Sent: Friday, March 07, 2003 8:55 AM
> To: Tracy Boehrer
> Subject: RE: Windows build works only as read-only (ITS#2349)
>
>
> I would imagine that JNDI sends to LDAP whatever attributes
> your application code gives it. If you didn't explicitly give
> it a value for "cn" then it's not being sent.
>
>   -- Howard Chu
>   Chief Architect, Symas Corp.       Director, Highland Sun
>   http://www.symas.com               http://highlandsun.com/hyc
>   Symas: Premier OpenSource Development and Support
>
> > -----Original Message-----
> > From: Tracy Boehrer [mailto:tboehrer@calltower.com]
> > Sent: Friday, March 07, 2003 6:48 AM
> > To: Howard Chu
> > Subject: RE: Windows build works only as read-only (ITS#2349)
> >
> >
> > This same problem happens via an update using JNDI's LDAP
> > provider.  Are you suggesting that it also is not including
> > the "cn" attribute?
> >
> > -----Original Message-----
> > From: Howard Chu [mailto:hyc@highlandsun.com]
> > Sent: Thursday, March 06, 2003 7:24 PM
> > To: Tracy Boehrer; openldap-its@OpenLDAP.org
> > Subject: RE: Windows build works only as read-only (ITS#2349)
> >
> >
> > This is not an OpenLDAP bug. Schema checking has been made
> > stricter in the
> > recent versions. The server has detected an error in your
> > LDIF that previous
> > versions ignored. Whatever attribute appears as the left-most
> > RDN of your DN
> > must be present in the body of the entry. Add the proper cn
> > attribute to your
> > LDIF and it'll be accepted.
> >
> >   -- Howard Chu
> >   Chief Architect, Symas Corp.       Director, Highland Sun
> >   http://www.symas.com               http://highlandsun.com/hyc
> >   Symas: Premier OpenSource Development and Support
> >
> > > -----Original Message-----
> > > From: owner-openldap-bugs@OpenLDAP.org
> > > [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of
> > tboehrer@calltower.com
> >
> > > Hi Howard,
> > >
> > > I'm not sure what you mean by an LDIF of the change since we are =
> > > attempting the change via another app via JavaMail.
> However, I've =
> > > attached the log.
> > >
> > > The error seems to be:
> > >
> > > send_ldap_result: err=3D16 matched=3D"" text=3D"value of naming =
> > > attribute 'cn' is not present in entry"
> > >
> > > I have also attached an LDIF (and the schema we use) that we
> > > use to init =
> > > the db.  slapadd also complains with the same error (about
> > > the missing =
> > > cn). =20
> > >
> > > However, under 2.1.10 both of these tests work.
> > >
> > > Thanks,
> > >
> > > Tracy
> >
> >
>