Re: Schema problem in .23

[Clif H. <cl...@di...>]

> 
> If you can dump the ldif for the entry, I will try to track it here
> 
> Graham.
> 
> On Thu, Jun 07, 2001 at 02:12:09PM -0500, Clif Harden wrote:
> > 
> > Graham,
> > 
> > I got a chance to look into the schema problem(s).
> > 
> > I think we have induced a "problem" into the .23 code.
> > 
> > I have a system that is still at .22 and it appears to be decoding
> > the objectclass information correctly, on a system at .23 there several
> > objectclasses do not decode correctly.  It varies on whether I hit my
> > x.500 server or my netscape servers.
> > 
> > I have installed your latest schema patch and it appears to have
> > the same problem.  I did not detect any new or additional problems.
> > 
> > I will send more information as I can find it.
> > 
> > Regards,
> > 
> > Clif Harden           INTERNET:  c-h...@ti...


Graham,

First problem I have found is that we are not 
parsing attribute SYNTAX lenghts correctly.

If an attribute has a length it is display properly,
if the attributer does not have a length a ) is 
given as it's lenght.

Example;

attributeTypes: ( 0.9.2342.19200300.100.1.40 NAME 'personalTitle' EQUALITY caseI
gnoreMatch ORDERING caseIgnoreOrderingMatch SUBSTR caseIgnoreSubstringsMatch SYN
TAX 1.3.6.1.4.1.1466.115.121.1.15{256} USAGE directoryOperation )

This will parse the length, 1.3.6.1.4.1.1466.115.121.1.15{256}, correctly .
This if from my x.500 directory.

attributeTypes: ( 1.3.6.1.4.1.42.2.27.5.1.1 NAME 'SolarisProjectID' DESC 'User D
efined Attribute' SYNTAX '1.3.6.1.4.1.1466.115.121.1.27' SINGLE-VALUE )

This will parse the length, 1.3.6.1.4.1.1466.115.121.1.27, incorrectly as
it will display a ) for length.  This if from my netscape ldap directory.


There is another problem, but I need to dig somemore before I 
attempt to describe it.


Regards,

Clif Harden           INTERNET:  c-h...@ti...