You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by "Barber, Dan (Contractor)" <Da...@Polycom.com> on 2007/06/14 01:09:09 UTC
Schema issues with Apache DS
Apache DS schema experts,
I'm a brand new user of Apache Directory and am trying to add support
for H.350. I've been able to convert several ldif files for the various
pieces of H.350 I want to include into schema files appropriate for LDAP
Studio. That all went perfectly. I exported them all as Apache Directory
ldif files, again without a hitch. However, when I try to import one of
those ldif files, for H.320 Identity, I get an error. I'm using LDAP
Studio to do the import.
The problem appears to be here:
attributetype (0.0.8.350.1.1.5.1.3
NAME 'h320IdentityExtension'
DESC 'Extension of terminal required to dial after initial PTSN
address is connected.'
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{120} )
which when exported to an Apache Directory LDIF file becomes
dn: m-oid=0.0.8.350.1.1.5.1.3, ou=attributeTypes, cn=h320Identity,
ou=schema
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-oid: 0.0.8.350.1.1.5.1.3
m-name: h320IdentityExtension
m-description: Extension of terminal required to dial after initial PTSN
address
is connected.
m-equality: caseIgnoreMatch
m-substr: caseIgnoreSubstringsMatch
m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
m-length: 120
The error that I get is on m-length. It appears that
1.3.6.1.4.1.1466.115.121.1.15 isn't supporting a length attribute.
Checking all over on the web I find several examples of a length
attribute being used with 1.3.6.1.4.1.1466.115.121.1.15.
Is there something that I'm missing? Is this a current shortcoming with
Apache DS 1.5?
Thanks for any help you can offer.
Sincerely,
Dan Barber
RE: Schema issues with Apache DS
Posted by "Barber, Dan (Contractor)" <Da...@Polycom.com>.
Thank you very much, I really appreciate the quick response :)
-----Original Message-----
From: pajbam@gmail.com [mailto:pajbam@gmail.com] On Behalf Of
Pierre-Arnaud Marcelot
Sent: Thursday, June 14, 2007 7:53 AM
To: users@directory.apache.org
Subject: Re: Schema issues with Apache DS
Ok,
I think I've found the bug. You were right, the error was on m-length.
The import fails because the m-length attribute doesn't exist in the
Apache
Meta schema bundled in the 1.5.0 version of Apache Directory Server.
The m-length attribute has been added on april 24th and Apache DS
1.5.0released on april 12th.
To avoid the problem what you can do is :
- whether removing the syntax length value from your schema (and wait
for
Apache DS 1.5.1 to fix the problem)
- or moving to the latest trunk version of Apache DS.
Sorry for the inconvenience...
P-A Marcelot
On 6/14/07, Pierre-Arnaud Marcelot < pa@marcelot.net> wrote:
>
> Hi Dan,
>
> I tried to import a schema defined with Apache Directory Studio
(formely
> LDAP Studio) containing an attribute type with syntax equals to '
> 1.3.6.1.4.1.1466.115.121.1.15' and syntax-length equals to '1234' in
the
> latest trunk version of Apache Directory Server, and it ended
successfully.
>
> Could you give us the complete error message please ?
>
> Pierre-Arnaud Marcelot
>
>
> On 6/14/07, Barber, Dan (Contractor) < Dan.Barber@polycom.com> wrote:
> >
> > Apache DS schema experts,
> >
> >
> >
> >
> >
> > I'm a brand new user of Apache Directory and am trying to add
support
> > for H.350. I've been able to convert several ldif files for the
various
> > pieces of H.350 I want to include into schema files appropriate for
LDAP
> >
> > Studio. That all went perfectly. I exported them all as Apache
Directory
> > ldif files, again without a hitch. However, when I try to import one
of
> > those ldif files, for H.320 Identity, I get an error. I'm using LDAP
> > Studio to do the import.
> >
> >
> >
> > The problem appears to be here:
> >
> >
> >
> >
> >
> > attributetype (0.0.8.350.1.1.5.1.3
> >
> >
> >
> > NAME 'h320IdentityExtension'
> >
> >
> >
> > DESC 'Extension of terminal required to dial after initial PTSN
> > address is connected.'
> >
> >
> >
> > EQUALITY caseIgnoreMatch
> >
> >
> >
> > SUBSTR caseIgnoreSubstringsMatch
> >
> >
> >
> > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{120} )
> >
> >
> >
> >
> >
> > which when exported to an Apache Directory LDIF file becomes
> >
> >
> >
> >
> >
> >
> >
> > dn: m-oid=0.0.8.350.1.1.5.1.3, ou=attributeTypes, cn=h320Identity,
> > ou=schema
> >
> >
> >
> > objectclass: metaAttributeType
> >
> >
> >
> > objectclass: metaTop
> >
> >
> >
> > objectclass: top
> >
> >
> >
> > m-oid: 0.0.8.350.1.1.5.1.3
> >
> >
> >
> > m-name: h320IdentityExtension
> >
> >
> >
> > m-description: Extension of terminal required to dial after initial
PTSN
> > address
> >
> >
> >
> > is connected.
> >
> >
> >
> > m-equality: caseIgnoreMatch
> >
> >
> >
> > m-substr: caseIgnoreSubstringsMatch
> >
> >
> >
> > m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
> >
> >
> >
> > m-length: 120
> >
> >
> >
> >
> >
> >
> >
> > The error that I get is on m-length. It appears that
> >
> > 1.3.6.1.4.1.1466.115.121.1.15 isn't supporting a length attribute.
> >
> > Checking all over on the web I find several examples of a length
> > attribute being used with 1.3.6.1.4.1.1466.115.121.1.15.
> >
> >
> >
> > Is there something that I'm missing? Is this a current shortcoming
with
> > Apache DS 1.5?
> >
> >
> >
> > Thanks for any help you can offer.
> >
> >
> >
> > Sincerely,
> >
> >
> >
> > Dan Barber
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
Re: Schema issues with Apache DS
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Ok,
I think I've found the bug. You were right, the error was on m-length.
The import fails because the m-length attribute doesn't exist in the Apache
Meta schema bundled in the 1.5.0 version of Apache Directory Server.
The m-length attribute has been added on april 24th and Apache DS
1.5.0released on april 12th.
To avoid the problem what you can do is :
- whether removing the syntax length value from your schema (and wait for
Apache DS 1.5.1 to fix the problem)
- or moving to the latest trunk version of Apache DS.
Sorry for the inconvenience...
P-A Marcelot
On 6/14/07, Pierre-Arnaud Marcelot < pa@marcelot.net> wrote:
>
> Hi Dan,
>
> I tried to import a schema defined with Apache Directory Studio (formely
> LDAP Studio) containing an attribute type with syntax equals to '
> 1.3.6.1.4.1.1466.115.121.1.15' and syntax-length equals to '1234' in the
> latest trunk version of Apache Directory Server, and it ended successfully.
>
> Could you give us the complete error message please ?
>
> Pierre-Arnaud Marcelot
>
>
> On 6/14/07, Barber, Dan (Contractor) < Dan.Barber@polycom.com> wrote:
> >
> > Apache DS schema experts,
> >
> >
> >
> >
> >
> > I'm a brand new user of Apache Directory and am trying to add support
> > for H.350. I've been able to convert several ldif files for the various
> > pieces of H.350 I want to include into schema files appropriate for LDAP
> >
> > Studio. That all went perfectly. I exported them all as Apache Directory
> > ldif files, again without a hitch. However, when I try to import one of
> > those ldif files, for H.320 Identity, I get an error. I'm using LDAP
> > Studio to do the import.
> >
> >
> >
> > The problem appears to be here:
> >
> >
> >
> >
> >
> > attributetype (0.0.8.350.1.1.5.1.3
> >
> >
> >
> > NAME 'h320IdentityExtension'
> >
> >
> >
> > DESC 'Extension of terminal required to dial after initial PTSN
> > address is connected.'
> >
> >
> >
> > EQUALITY caseIgnoreMatch
> >
> >
> >
> > SUBSTR caseIgnoreSubstringsMatch
> >
> >
> >
> > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{120} )
> >
> >
> >
> >
> >
> > which when exported to an Apache Directory LDIF file becomes
> >
> >
> >
> >
> >
> >
> >
> > dn: m-oid=0.0.8.350.1.1.5.1.3, ou=attributeTypes, cn=h320Identity,
> > ou=schema
> >
> >
> >
> > objectclass: metaAttributeType
> >
> >
> >
> > objectclass: metaTop
> >
> >
> >
> > objectclass: top
> >
> >
> >
> > m-oid: 0.0.8.350.1.1.5.1.3
> >
> >
> >
> > m-name: h320IdentityExtension
> >
> >
> >
> > m-description: Extension of terminal required to dial after initial PTSN
> > address
> >
> >
> >
> > is connected.
> >
> >
> >
> > m-equality: caseIgnoreMatch
> >
> >
> >
> > m-substr: caseIgnoreSubstringsMatch
> >
> >
> >
> > m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
> >
> >
> >
> > m-length: 120
> >
> >
> >
> >
> >
> >
> >
> > The error that I get is on m-length. It appears that
> >
> > 1.3.6.1.4.1.1466.115.121.1.15 isn't supporting a length attribute.
> >
> > Checking all over on the web I find several examples of a length
> > attribute being used with 1.3.6.1.4.1.1466.115.121.1.15.
> >
> >
> >
> > Is there something that I'm missing? Is this a current shortcoming with
> > Apache DS 1.5?
> >
> >
> >
> > Thanks for any help you can offer.
> >
> >
> >
> > Sincerely,
> >
> >
> >
> > Dan Barber
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
Re: Schema issues with Apache DS
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Dan,
I tried to import a schema defined with Apache Directory Studio (formely
LDAP Studio) containing an attribute type with syntax equals to '
1.3.6.1.4.1.1466.115.121.1.15' and syntax-length equals to '1234' in the
latest trunk version of Apache Directory Server, and it ended successfully.
Could you give us the complete error message please ?
Pierre-Arnaud Marcelot
On 6/14/07, Barber, Dan (Contractor) < Dan.Barber@polycom.com> wrote:
>
> Apache DS schema experts,
>
>
>
>
>
> I'm a brand new user of Apache Directory and am trying to add support
> for H.350. I've been able to convert several ldif files for the various
> pieces of H.350 I want to include into schema files appropriate for LDAP
> Studio. That all went perfectly. I exported them all as Apache Directory
> ldif files, again without a hitch. However, when I try to import one of
> those ldif files, for H.320 Identity, I get an error. I'm using LDAP
> Studio to do the import.
>
>
>
> The problem appears to be here:
>
>
>
>
>
> attributetype (0.0.8.350.1.1.5.1.3
>
>
>
> NAME 'h320IdentityExtension'
>
>
>
> DESC 'Extension of terminal required to dial after initial PTSN
> address is connected.'
>
>
>
> EQUALITY caseIgnoreMatch
>
>
>
> SUBSTR caseIgnoreSubstringsMatch
>
>
>
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{120} )
>
>
>
>
>
> which when exported to an Apache Directory LDIF file becomes
>
>
>
>
>
>
>
> dn: m-oid=0.0.8.350.1.1.5.1.3, ou=attributeTypes, cn=h320Identity,
> ou=schema
>
>
>
> objectclass: metaAttributeType
>
>
>
> objectclass: metaTop
>
>
>
> objectclass: top
>
>
>
> m-oid: 0.0.8.350.1.1.5.1.3
>
>
>
> m-name: h320IdentityExtension
>
>
>
> m-description: Extension of terminal required to dial after initial PTSN
> address
>
>
>
> is connected.
>
>
>
> m-equality: caseIgnoreMatch
>
>
>
> m-substr: caseIgnoreSubstringsMatch
>
>
>
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
>
>
>
> m-length: 120
>
>
>
>
>
>
>
> The error that I get is on m-length. It appears that
>
> 1.3.6.1.4.1.1466.115.121.1.15 isn't supporting a length attribute.
>
> Checking all over on the web I find several examples of a length
> attribute being used with 1.3.6.1.4.1.1466.115.121.1.15.
>
>
>
> Is there something that I'm missing? Is this a current shortcoming with
> Apache DS 1.5?
>
>
>
> Thanks for any help you can offer.
>
>
>
> Sincerely,
>
>
>
> Dan Barber
>
>
>
>
>
>
>
>
>
>
>
>