Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com
 designates 209.85.198.232 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=E7J855dYyeqRMiP0CM5id+0IgYKdlNSXvF3vRuMRGIGYntdxHoup3eqwrmmRaXl8us0dDmo6LEljr3So0HWU7wmjFU+qzpTimFr/iHo40GE9jCyc2rN4dBcz+kNCGz5IJ/yvpD7KbgMzBKU475/9Et5kHazmDFxpUdeAVZQHrIE=
Message-ID: <a32f6b020805090235m515781d7p59e82bda348c3c24@mail.gmail.com>
Date: Fri, 9 May 2008 05:35:30 -0400
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: users@directory.apache.org
Subject: Re: adding schema
In-Reply-To: <36041a720805090048k536890d3p8edf2ee6fcde6d80@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_6309_24591627.1210325730970"
References: <5757c1aa0805080620n606134b0u10aea675584eb38e@mail.gmail.com>
	 <36041a720805080628l46413a71w2f34e18f0fa2889c@mail.gmail.com>
	 <a32f6b020805080700keb7c570t2c06e7d735ef0606@mail.gmail.com>
	 <36041a720805080705h6d7c8e7dh2510ac792a558e19@mail.gmail.com>
	 <4823E39F.3000100@apache.org> <4823E8FE.8070804@apache.org>
	 <36041a720805090048k536890d3p8edf2ee6fcde6d80@mail.gmail.com>

------=_Part_6309_24591627.1210325730970
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Lowercase the objectClass to objectclass.  Same with attributeType make sur=
e
it is all lowercase.  We followed the protocol specification with this.
OpenLDAP schemas used to have more liberty but they're changing it too.
Just take a look at their latest schema files.  They are using the proper
order and case now.

Alex

On Fri, May 9, 2008 at 3:48 AM, Jeroen Vriesman <linuxificator@gmail.com>
wrote:

> Hi,
>
> treid to import schema's from openldap.
>
> The import function seems to be very strict.
>
> First, I got the error:
> The file '/root/schema/hivos.schema' can not be read correctly.
> Line: 23, Column: 9, Cause: unexpected token: NAME
>
> When I look in the schema file:
> attributetype ( 1.3.6.1.4.1.17416.0.255.1.4
>        DESC 'absolute shared folder location'
>        NAME 'sharedFolderLocation'
>        EQUALITY caseExactIA5Match
>        SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
>
> That one works when I change it to:
> attributetype ( 1.3.6.1.4.1.17416.0.255.1.4
>        NAME 'sharedFolderLocation'
>        DESC 'absolute shared folder location'
>        EQUALITY caseExactIA5Match
>        SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
>
> So the import function always expects the NAME first, openldap doesn't ca=
re
> about that.
>
> After correcting this, I get the error:
> The file '/root/schema/hivos.schema' can not be read correctly.
> Line: 121, Column: 1, Cause: expecting "END", found 'objectClass'
>
> In the openldap schema file this is where the objectclasses start:
> attributetype ( 1.3.6.1.4.1.17416.0.255.1.19
>        NAME 'horoThuis'
>        DESC 'True if person is not coming from an internal IP'
>        EQUALITY booleanMatch
>        SYNTAX 1.3.6.1.4.1.1466.115.121.1.7
>        SINGLE-VALUE )
>
> objectClass ( 1.3.6.1.4.1.17416.0.255.0.14 NAME 'hivosMailAccount' SUP to=
p
> AUXILIARY   <----- line 121
>        DESC 'Mail account object as used by Hivos'
>        MUST ( mail $ homeDirectory $ mailbox $ userPassword )
>        MAY ( quota $ subscribeToSharedFolder $ isSharedFolder $ hivosIsIn=
 $
> horoAanwezig $ horoInDienst $ horoThuis ) )
>
> The number of ( and )'s are correct in the file, so I don't see what it
> actually expects.
>
> Regards,
> Jeroen.
>
>
>
>
>
>
>
> On Fri, May 9, 2008 at 8:02 AM, Emmanuel Lecharny <elecharny@apache.org>
> wrote:
>
> > Stefan Seelmann wrote:
> >
> >>
> >>  and most of the time admins don't want to start huge complex
> >>> interfaces to add or edit a schema, working with simple text files is
> (at
> >>> least for me) the easyest way.
> >>>
> >>>
> >>>
> >>
> >> That is right. Perhaps we should try to extract the schema import and
> >> export to a separate library, then we could use it for CLI and GUI.
> >>
> >>
> > The best idea, and we already discussed about it, would be to simply dr=
op
> > the new schema into a directory, and either restart the server, or use =
a
> CLI
> > to ask the server to load this new schema, or to send an extended reque=
st
> to
> > the server to tell it to load the file.
> >
> > We have everything we need to do that, except the glue...
> >
> >> Regards,
> >> Stefan
> >>
> >>
> >>
> >
> >
> > --
> > --
> > cordialement, regards,
> > Emmanuel L=E9charny
> > www.iktek.com
> > directory.apache.org
> >
> >
> >
>

------=_Part_6309_24591627.1210325730970--