You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by Pierre Smits <pi...@gmail.com> on 2008/05/08 15:20:29 UTC

adding schema

I am testing the 1.5.2 windows version.

When accessing the running ds service with apache studio I see the samba
schema. However, when creating new entries I cannot select samba objects.

How do I make the samba schema available in the list of selectable objects?
Do I need to configure something?


Regards,

Pierre

Re: adding schema

Posted by Alex Karasulu <ak...@apache.org>.
Guess Samba schema depends on Nis schema attributes or vica-versa.  That's
why you had a problem.

Alex

On Fri, May 9, 2008 at 8:32 AM, Pierre Smits <pi...@gmail.com> wrote:

> Reinstall the server, set m-disabled for nis to FALSE and then set
> m-disabled for samba to FALSE did the trick. Samba objects classes are now
> available.
>
> Thanks.
>
>
> On Fri, May 9, 2008 at 2:25 PM, Pierre Smits <pi...@gmail.com>
> wrote:
>
> > I see that nis (which is has m-oid= 1.3.6.1.1.1.1.0) has m-disabled =
> true,
> > but see no way to change te value.
> >
> > Do you know how I could go about it?
> >
> >
> > On Fri, May 9, 2008 at 11:16 AM, Jeroen Vriesman <
> linuxificator@gmail.com>
> > wrote:
> >
> >> Hi,
> >>
> >> maybe the schema defining attribute type 1.3.6.1.1.1.1.0 is disabled?
> >>
> >> Looking at the samba schema I see:
> >> m-dependencies: system
> >> m-dependencies: core
> >> m-dependencies: inetorgperson
> >> m-dependencies: nis
> >>
> >> did you also set m-disabled=FALSE in inetorgperson and nis?
> >>
> >> On Fri, May 9, 2008 at 11:09 AM, Pierre Smits <pi...@gmail.com>
> >> wrote:
> >>
> >> > The verion I am using is apacheds 1.5.2 with jvm 1.5.
> >> >
> >> > It happened both on the linux and the windows version.
> >> >
> >> > On Thu, May 8, 2008 at 11:40 PM, Alex Karasulu <ak...@apache.org>
> >> > wrote:
> >> >
> >> > > Give me some information to go on: platform, jvm, and ApacheDS
> >> version.
> >> > > Also turn on debugging after clearing out the log file and send it
> >> over.
> >> > >
> >> > > Alex
> >> > >
> >> > > On Thu, May 8, 2008 at 11:19 AM, Pierre Smits <
> pierre.smits@gmail.com
> >> >
> >> > > wrote:
> >> > >
> >> > > > When enabling the samba schema via above mentioned method and
> >> > restarting
> >> > > > the
> >> > > > server again, I get following error message:
> >> > > >
> >> > > >
> >> > > > Error while opening connection
> >> > > > [LDAP: error code 80 - failed on search operation: attributeType
> w/
> >> OID
> >> > > > 1.3.6.1.1.1.1.0 not registered!]
> >> > > >  [LDAP: error code 80 - failed on search operation: attributeType
> w/
> >> > OID
> >> > > > 1.3.6.1.1.1.1.0 not registered!]
> >> > > >  Error occurred while loading schema, using default schema
> >> > > >
> >> > > > How do I correct this?
> >> > > >
> >> > > > Regards,
> >> > > >
> >> > > > Pierre
> >> > > >
> >> > > >
> >> > > > On Thu, May 8, 2008 at 3:28 PM, Jeroen Vriesman <
> >> > linuxificator@gmail.com
> >> > > >
> >> > > > wrote:
> >> > > >
> >> > > > > I had the same problem some time ago,
> >> > > > >
> >> > > > > under cn=admin,ou=shema you can see that "m-disabled" is TRUE,
> set
> >> it
> >> > > to
> >> > > > > FALSE
> >> > > > >
> >> > > > >
> >> > > > > By the way, another question for the rest of us, is there an
> easy
> >> way
> >> > > to
> >> > > > > convert the openldap schema's to apachds (is it enough to
> convert
> >> > them
> >> > > > and
> >> > > > > add them under ou=schema?)
> >> > > > >
> >> > > > > what I want is to take the file of an openldap schema and just
> >> > ldap-add
> >> > > > > some
> >> > > > > converted stuff to apache on the commandline, is there such a
> >> > > converter?
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > On Thu, May 8, 2008 at 3:20 PM, Pierre Smits <
> >> pierre.smits@gmail.com
> >> > >
> >> > > > > wrote:
> >> > > > >
> >> > > > > > I am testing the 1.5.2 windows version.
> >> > > > > >
> >> > > > > > When accessing the running ds service with apache studio I see
> >> the
> >> > > > samba
> >> > > > > > schema. However, when creating new entries I cannot select
> samba
> >> > > > objects.
> >> > > > > >
> >> > > > > > How do I make the samba schema available in the list of
> >> selectable
> >> > > > > > objects?
> >> > > > > > Do I need to configure something?
> >> > > > > >
> >> > > > > >
> >> > > > > > Regards,
> >> > > > > >
> >> > > > > > Pierre
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>

Re: adding schema

Posted by Alex Karasulu <ak...@apache.org>.
Hmmm don't remember.  Feel free to point me in the direction of the latest
and greatest and I'll upgrade it.

Alex

On Fri, May 9, 2008 at 8:40 AM, Pierre Smits <pi...@gmail.com> wrote:

> To which samba version does the samba schema adhere?
>
>
> On Fri, May 9, 2008 at 2:32 PM, Pierre Smits <pi...@gmail.com>
> wrote:
>
> > Reinstall the server, set m-disabled for nis to FALSE and then set
> > m-disabled for samba to FALSE did the trick. Samba objects classes are
> now
> > available.
> >
> > Thanks.
> >
> >
> >
> > On Fri, May 9, 2008 at 2:25 PM, Pierre Smits <pi...@gmail.com>
> > wrote:
> >
> >> I see that nis (which is has m-oid= 1.3.6.1.1.1.1.0) has m-disabled =
> >> true, but see no way to change te value.
> >>
> >> Do you know how I could go about it?
> >>
> >>
> >> On Fri, May 9, 2008 at 11:16 AM, Jeroen Vriesman <
> linuxificator@gmail.com>
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> maybe the schema defining attribute type 1.3.6.1.1.1.1.0 is disabled?
> >>>
> >>> Looking at the samba schema I see:
> >>> m-dependencies: system
> >>> m-dependencies: core
> >>> m-dependencies: inetorgperson
> >>> m-dependencies: nis
> >>>
> >>> did you also set m-disabled=FALSE in inetorgperson and nis?
> >>>
> >>> On Fri, May 9, 2008 at 11:09 AM, Pierre Smits <pi...@gmail.com>
> >>> wrote:
> >>>
> >>> > The verion I am using is apacheds 1.5.2 with jvm 1.5.
> >>> >
> >>> > It happened both on the linux and the windows version.
> >>> >
> >>> > On Thu, May 8, 2008 at 11:40 PM, Alex Karasulu <akarasulu@apache.org
> >
> >>> > wrote:
> >>> >
> >>> > > Give me some information to go on: platform, jvm, and ApacheDS
> >>> version.
> >>> > > Also turn on debugging after clearing out the log file and send it
> >>> over.
> >>> > >
> >>> > > Alex
> >>> > >
> >>> > > On Thu, May 8, 2008 at 11:19 AM, Pierre Smits <
> >>> pierre.smits@gmail.com>
> >>> > > wrote:
> >>> > >
> >>> > > > When enabling the samba schema via above mentioned method and
> >>> > restarting
> >>> > > > the
> >>> > > > server again, I get following error message:
> >>> > > >
> >>> > > >
> >>> > > > Error while opening connection
> >>> > > > [LDAP: error code 80 - failed on search operation: attributeType
> w/
> >>> OID
> >>> > > > 1.3.6.1.1.1.1.0 not registered!]
> >>> > > >  [LDAP: error code 80 - failed on search operation: attributeType
> >>> w/
> >>> > OID
> >>> > > > 1.3.6.1.1.1.1.0 not registered!]
> >>> > > >  Error occurred while loading schema, using default schema
> >>> > > >
> >>> > > > How do I correct this?
> >>> > > >
> >>> > > > Regards,
> >>> > > >
> >>> > > > Pierre
> >>> > > >
> >>> > > >
> >>> > > > On Thu, May 8, 2008 at 3:28 PM, Jeroen Vriesman <
> >>> > linuxificator@gmail.com
> >>> > > >
> >>> > > > wrote:
> >>> > > >
> >>> > > > > I had the same problem some time ago,
> >>> > > > >
> >>> > > > > under cn=admin,ou=shema you can see that "m-disabled" is TRUE,
> >>> set it
> >>> > > to
> >>> > > > > FALSE
> >>> > > > >
> >>> > > > >
> >>> > > > > By the way, another question for the rest of us, is there an
> easy
> >>> way
> >>> > > to
> >>> > > > > convert the openldap schema's to apachds (is it enough to
> convert
> >>> > them
> >>> > > > and
> >>> > > > > add them under ou=schema?)
> >>> > > > >
> >>> > > > > what I want is to take the file of an openldap schema and just
> >>> > ldap-add
> >>> > > > > some
> >>> > > > > converted stuff to apache on the commandline, is there such a
> >>> > > converter?
> >>> > > > >
> >>> > > > >
> >>> > > > >
> >>> > > > > On Thu, May 8, 2008 at 3:20 PM, Pierre Smits <
> >>> pierre.smits@gmail.com
> >>> > >
> >>> > > > > wrote:
> >>> > > > >
> >>> > > > > > I am testing the 1.5.2 windows version.
> >>> > > > > >
> >>> > > > > > When accessing the running ds service with apache studio I
> see
> >>> the
> >>> > > > samba
> >>> > > > > > schema. However, when creating new entries I cannot select
> >>> samba
> >>> > > > objects.
> >>> > > > > >
> >>> > > > > > How do I make the samba schema available in the list of
> >>> selectable
> >>> > > > > > objects?
> >>> > > > > > Do I need to configure something?
> >>> > > > > >
> >>> > > > > >
> >>> > > > > > Regards,
> >>> > > > > >
> >>> > > > > > Pierre
> >>> > > > > >
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> >>
> >>
> >
>

Re: adding schema

Posted by Pierre Smits <pi...@gmail.com>.
To which samba version does the samba schema adhere?


On Fri, May 9, 2008 at 2:32 PM, Pierre Smits <pi...@gmail.com> wrote:

> Reinstall the server, set m-disabled for nis to FALSE and then set
> m-disabled for samba to FALSE did the trick. Samba objects classes are now
> available.
>
> Thanks.
>
>
>
> On Fri, May 9, 2008 at 2:25 PM, Pierre Smits <pi...@gmail.com>
> wrote:
>
>> I see that nis (which is has m-oid= 1.3.6.1.1.1.1.0) has m-disabled =
>> true, but see no way to change te value.
>>
>> Do you know how I could go about it?
>>
>>
>> On Fri, May 9, 2008 at 11:16 AM, Jeroen Vriesman <li...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> maybe the schema defining attribute type 1.3.6.1.1.1.1.0 is disabled?
>>>
>>> Looking at the samba schema I see:
>>> m-dependencies: system
>>> m-dependencies: core
>>> m-dependencies: inetorgperson
>>> m-dependencies: nis
>>>
>>> did you also set m-disabled=FALSE in inetorgperson and nis?
>>>
>>> On Fri, May 9, 2008 at 11:09 AM, Pierre Smits <pi...@gmail.com>
>>> wrote:
>>>
>>> > The verion I am using is apacheds 1.5.2 with jvm 1.5.
>>> >
>>> > It happened both on the linux and the windows version.
>>> >
>>> > On Thu, May 8, 2008 at 11:40 PM, Alex Karasulu <ak...@apache.org>
>>> > wrote:
>>> >
>>> > > Give me some information to go on: platform, jvm, and ApacheDS
>>> version.
>>> > > Also turn on debugging after clearing out the log file and send it
>>> over.
>>> > >
>>> > > Alex
>>> > >
>>> > > On Thu, May 8, 2008 at 11:19 AM, Pierre Smits <
>>> pierre.smits@gmail.com>
>>> > > wrote:
>>> > >
>>> > > > When enabling the samba schema via above mentioned method and
>>> > restarting
>>> > > > the
>>> > > > server again, I get following error message:
>>> > > >
>>> > > >
>>> > > > Error while opening connection
>>> > > > [LDAP: error code 80 - failed on search operation: attributeType w/
>>> OID
>>> > > > 1.3.6.1.1.1.1.0 not registered!]
>>> > > >  [LDAP: error code 80 - failed on search operation: attributeType
>>> w/
>>> > OID
>>> > > > 1.3.6.1.1.1.1.0 not registered!]
>>> > > >  Error occurred while loading schema, using default schema
>>> > > >
>>> > > > How do I correct this?
>>> > > >
>>> > > > Regards,
>>> > > >
>>> > > > Pierre
>>> > > >
>>> > > >
>>> > > > On Thu, May 8, 2008 at 3:28 PM, Jeroen Vriesman <
>>> > linuxificator@gmail.com
>>> > > >
>>> > > > wrote:
>>> > > >
>>> > > > > I had the same problem some time ago,
>>> > > > >
>>> > > > > under cn=admin,ou=shema you can see that "m-disabled" is TRUE,
>>> set it
>>> > > to
>>> > > > > FALSE
>>> > > > >
>>> > > > >
>>> > > > > By the way, another question for the rest of us, is there an easy
>>> way
>>> > > to
>>> > > > > convert the openldap schema's to apachds (is it enough to convert
>>> > them
>>> > > > and
>>> > > > > add them under ou=schema?)
>>> > > > >
>>> > > > > what I want is to take the file of an openldap schema and just
>>> > ldap-add
>>> > > > > some
>>> > > > > converted stuff to apache on the commandline, is there such a
>>> > > converter?
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > > On Thu, May 8, 2008 at 3:20 PM, Pierre Smits <
>>> pierre.smits@gmail.com
>>> > >
>>> > > > > wrote:
>>> > > > >
>>> > > > > > I am testing the 1.5.2 windows version.
>>> > > > > >
>>> > > > > > When accessing the running ds service with apache studio I see
>>> the
>>> > > > samba
>>> > > > > > schema. However, when creating new entries I cannot select
>>> samba
>>> > > > objects.
>>> > > > > >
>>> > > > > > How do I make the samba schema available in the list of
>>> selectable
>>> > > > > > objects?
>>> > > > > > Do I need to configure something?
>>> > > > > >
>>> > > > > >
>>> > > > > > Regards,
>>> > > > > >
>>> > > > > > Pierre
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>
>>
>

Re: adding schema

Posted by Pierre Smits <pi...@gmail.com>.
Reinstall the server, set m-disabled for nis to FALSE and then set
m-disabled for samba to FALSE did the trick. Samba objects classes are now
available.

Thanks.


On Fri, May 9, 2008 at 2:25 PM, Pierre Smits <pi...@gmail.com> wrote:

> I see that nis (which is has m-oid= 1.3.6.1.1.1.1.0) has m-disabled = true,
> but see no way to change te value.
>
> Do you know how I could go about it?
>
>
> On Fri, May 9, 2008 at 11:16 AM, Jeroen Vriesman <li...@gmail.com>
> wrote:
>
>> Hi,
>>
>> maybe the schema defining attribute type 1.3.6.1.1.1.1.0 is disabled?
>>
>> Looking at the samba schema I see:
>> m-dependencies: system
>> m-dependencies: core
>> m-dependencies: inetorgperson
>> m-dependencies: nis
>>
>> did you also set m-disabled=FALSE in inetorgperson and nis?
>>
>> On Fri, May 9, 2008 at 11:09 AM, Pierre Smits <pi...@gmail.com>
>> wrote:
>>
>> > The verion I am using is apacheds 1.5.2 with jvm 1.5.
>> >
>> > It happened both on the linux and the windows version.
>> >
>> > On Thu, May 8, 2008 at 11:40 PM, Alex Karasulu <ak...@apache.org>
>> > wrote:
>> >
>> > > Give me some information to go on: platform, jvm, and ApacheDS
>> version.
>> > > Also turn on debugging after clearing out the log file and send it
>> over.
>> > >
>> > > Alex
>> > >
>> > > On Thu, May 8, 2008 at 11:19 AM, Pierre Smits <pierre.smits@gmail.com
>> >
>> > > wrote:
>> > >
>> > > > When enabling the samba schema via above mentioned method and
>> > restarting
>> > > > the
>> > > > server again, I get following error message:
>> > > >
>> > > >
>> > > > Error while opening connection
>> > > > [LDAP: error code 80 - failed on search operation: attributeType w/
>> OID
>> > > > 1.3.6.1.1.1.1.0 not registered!]
>> > > >  [LDAP: error code 80 - failed on search operation: attributeType w/
>> > OID
>> > > > 1.3.6.1.1.1.1.0 not registered!]
>> > > >  Error occurred while loading schema, using default schema
>> > > >
>> > > > How do I correct this?
>> > > >
>> > > > Regards,
>> > > >
>> > > > Pierre
>> > > >
>> > > >
>> > > > On Thu, May 8, 2008 at 3:28 PM, Jeroen Vriesman <
>> > linuxificator@gmail.com
>> > > >
>> > > > wrote:
>> > > >
>> > > > > I had the same problem some time ago,
>> > > > >
>> > > > > under cn=admin,ou=shema you can see that "m-disabled" is TRUE, set
>> it
>> > > to
>> > > > > FALSE
>> > > > >
>> > > > >
>> > > > > By the way, another question for the rest of us, is there an easy
>> way
>> > > to
>> > > > > convert the openldap schema's to apachds (is it enough to convert
>> > them
>> > > > and
>> > > > > add them under ou=schema?)
>> > > > >
>> > > > > what I want is to take the file of an openldap schema and just
>> > ldap-add
>> > > > > some
>> > > > > converted stuff to apache on the commandline, is there such a
>> > > converter?
>> > > > >
>> > > > >
>> > > > >
>> > > > > On Thu, May 8, 2008 at 3:20 PM, Pierre Smits <
>> pierre.smits@gmail.com
>> > >
>> > > > > wrote:
>> > > > >
>> > > > > > I am testing the 1.5.2 windows version.
>> > > > > >
>> > > > > > When accessing the running ds service with apache studio I see
>> the
>> > > > samba
>> > > > > > schema. However, when creating new entries I cannot select samba
>> > > > objects.
>> > > > > >
>> > > > > > How do I make the samba schema available in the list of
>> selectable
>> > > > > > objects?
>> > > > > > Do I need to configure something?
>> > > > > >
>> > > > > >
>> > > > > > Regards,
>> > > > > >
>> > > > > > Pierre
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

Re: adding schema

Posted by Jeroen Vriesman <li...@gmail.com>.
You can change the value with any ldap editor (I use phpldapadmin for it)

On Fri, May 9, 2008 at 2:25 PM, Pierre Smits <pi...@gmail.com> wrote:

> I see that nis (which is has m-oid= 1.3.6.1.1.1.1.0) has m-disabled = true,
> but see no way to change te value.
>
> Do you know how I could go about it?
>
> On Fri, May 9, 2008 at 11:16 AM, Jeroen Vriesman <li...@gmail.com>
> wrote:
>
> > Hi,
> >
> > maybe the schema defining attribute type 1.3.6.1.1.1.1.0 is disabled?
> >
> > Looking at the samba schema I see:
> > m-dependencies: system
> > m-dependencies: core
> > m-dependencies: inetorgperson
> > m-dependencies: nis
> >
> > did you also set m-disabled=FALSE in inetorgperson and nis?
> >
> > On Fri, May 9, 2008 at 11:09 AM, Pierre Smits <pi...@gmail.com>
> > wrote:
> >
> > > The verion I am using is apacheds 1.5.2 with jvm 1.5.
> > >
> > > It happened both on the linux and the windows version.
> > >
> > > On Thu, May 8, 2008 at 11:40 PM, Alex Karasulu <ak...@apache.org>
> > > wrote:
> > >
> > > > Give me some information to go on: platform, jvm, and ApacheDS
> version.
> > > > Also turn on debugging after clearing out the log file and send it
> > over.
> > > >
> > > > Alex
> > > >
> > > > On Thu, May 8, 2008 at 11:19 AM, Pierre Smits <
> pierre.smits@gmail.com>
> > > > wrote:
> > > >
> > > > > When enabling the samba schema via above mentioned method and
> > > restarting
> > > > > the
> > > > > server again, I get following error message:
> > > > >
> > > > >
> > > > > Error while opening connection
> > > > > [LDAP: error code 80 - failed on search operation: attributeType w/
> > OID
> > > > > 1.3.6.1.1.1.1.0 not registered!]
> > > > >  [LDAP: error code 80 - failed on search operation: attributeType
> w/
> > > OID
> > > > > 1.3.6.1.1.1.1.0 not registered!]
> > > > >  Error occurred while loading schema, using default schema
> > > > >
> > > > > How do I correct this?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Pierre
> > > > >
> > > > >
> > > > > On Thu, May 8, 2008 at 3:28 PM, Jeroen Vriesman <
> > > linuxificator@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > I had the same problem some time ago,
> > > > > >
> > > > > > under cn=admin,ou=shema you can see that "m-disabled" is TRUE,
> set
> > it
> > > > to
> > > > > > FALSE
> > > > > >
> > > > > >
> > > > > > By the way, another question for the rest of us, is there an easy
> > way
> > > > to
> > > > > > convert the openldap schema's to apachds (is it enough to convert
> > > them
> > > > > and
> > > > > > add them under ou=schema?)
> > > > > >
> > > > > > what I want is to take the file of an openldap schema and just
> > > ldap-add
> > > > > > some
> > > > > > converted stuff to apache on the commandline, is there such a
> > > > converter?
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Thu, May 8, 2008 at 3:20 PM, Pierre Smits <
> > pierre.smits@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > I am testing the 1.5.2 windows version.
> > > > > > >
> > > > > > > When accessing the running ds service with apache studio I see
> > the
> > > > > samba
> > > > > > > schema. However, when creating new entries I cannot select
> samba
> > > > > objects.
> > > > > > >
> > > > > > > How do I make the samba schema available in the list of
> > selectable
> > > > > > > objects?
> > > > > > > Do I need to configure something?
> > > > > > >
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Pierre
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: adding schema

Posted by Pierre Smits <pi...@gmail.com>.
I see that nis (which is has m-oid= 1.3.6.1.1.1.1.0) has m-disabled = true,
but see no way to change te value.

Do you know how I could go about it?

On Fri, May 9, 2008 at 11:16 AM, Jeroen Vriesman <li...@gmail.com>
wrote:

> Hi,
>
> maybe the schema defining attribute type 1.3.6.1.1.1.1.0 is disabled?
>
> Looking at the samba schema I see:
> m-dependencies: system
> m-dependencies: core
> m-dependencies: inetorgperson
> m-dependencies: nis
>
> did you also set m-disabled=FALSE in inetorgperson and nis?
>
> On Fri, May 9, 2008 at 11:09 AM, Pierre Smits <pi...@gmail.com>
> wrote:
>
> > The verion I am using is apacheds 1.5.2 with jvm 1.5.
> >
> > It happened both on the linux and the windows version.
> >
> > On Thu, May 8, 2008 at 11:40 PM, Alex Karasulu <ak...@apache.org>
> > wrote:
> >
> > > Give me some information to go on: platform, jvm, and ApacheDS version.
> > > Also turn on debugging after clearing out the log file and send it
> over.
> > >
> > > Alex
> > >
> > > On Thu, May 8, 2008 at 11:19 AM, Pierre Smits <pi...@gmail.com>
> > > wrote:
> > >
> > > > When enabling the samba schema via above mentioned method and
> > restarting
> > > > the
> > > > server again, I get following error message:
> > > >
> > > >
> > > > Error while opening connection
> > > > [LDAP: error code 80 - failed on search operation: attributeType w/
> OID
> > > > 1.3.6.1.1.1.1.0 not registered!]
> > > >  [LDAP: error code 80 - failed on search operation: attributeType w/
> > OID
> > > > 1.3.6.1.1.1.1.0 not registered!]
> > > >  Error occurred while loading schema, using default schema
> > > >
> > > > How do I correct this?
> > > >
> > > > Regards,
> > > >
> > > > Pierre
> > > >
> > > >
> > > > On Thu, May 8, 2008 at 3:28 PM, Jeroen Vriesman <
> > linuxificator@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > I had the same problem some time ago,
> > > > >
> > > > > under cn=admin,ou=shema you can see that "m-disabled" is TRUE, set
> it
> > > to
> > > > > FALSE
> > > > >
> > > > >
> > > > > By the way, another question for the rest of us, is there an easy
> way
> > > to
> > > > > convert the openldap schema's to apachds (is it enough to convert
> > them
> > > > and
> > > > > add them under ou=schema?)
> > > > >
> > > > > what I want is to take the file of an openldap schema and just
> > ldap-add
> > > > > some
> > > > > converted stuff to apache on the commandline, is there such a
> > > converter?
> > > > >
> > > > >
> > > > >
> > > > > On Thu, May 8, 2008 at 3:20 PM, Pierre Smits <
> pierre.smits@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > I am testing the 1.5.2 windows version.
> > > > > >
> > > > > > When accessing the running ds service with apache studio I see
> the
> > > > samba
> > > > > > schema. However, when creating new entries I cannot select samba
> > > > objects.
> > > > > >
> > > > > > How do I make the samba schema available in the list of
> selectable
> > > > > > objects?
> > > > > > Do I need to configure something?
> > > > > >
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Pierre
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: adding schema

Posted by Jeroen Vriesman <li...@gmail.com>.
Hi,

maybe the schema defining attribute type 1.3.6.1.1.1.1.0 is disabled?

Looking at the samba schema I see:
m-dependencies: system
m-dependencies: core
m-dependencies: inetorgperson
m-dependencies: nis

did you also set m-disabled=FALSE in inetorgperson and nis?

On Fri, May 9, 2008 at 11:09 AM, Pierre Smits <pi...@gmail.com>
wrote:

> The verion I am using is apacheds 1.5.2 with jvm 1.5.
>
> It happened both on the linux and the windows version.
>
> On Thu, May 8, 2008 at 11:40 PM, Alex Karasulu <ak...@apache.org>
> wrote:
>
> > Give me some information to go on: platform, jvm, and ApacheDS version.
> > Also turn on debugging after clearing out the log file and send it over.
> >
> > Alex
> >
> > On Thu, May 8, 2008 at 11:19 AM, Pierre Smits <pi...@gmail.com>
> > wrote:
> >
> > > When enabling the samba schema via above mentioned method and
> restarting
> > > the
> > > server again, I get following error message:
> > >
> > >
> > > Error while opening connection
> > > [LDAP: error code 80 - failed on search operation: attributeType w/ OID
> > > 1.3.6.1.1.1.1.0 not registered!]
> > >  [LDAP: error code 80 - failed on search operation: attributeType w/
> OID
> > > 1.3.6.1.1.1.1.0 not registered!]
> > >  Error occurred while loading schema, using default schema
> > >
> > > How do I correct this?
> > >
> > > Regards,
> > >
> > > Pierre
> > >
> > >
> > > On Thu, May 8, 2008 at 3:28 PM, Jeroen Vriesman <
> linuxificator@gmail.com
> > >
> > > wrote:
> > >
> > > > I had the same problem some time ago,
> > > >
> > > > under cn=admin,ou=shema you can see that "m-disabled" is TRUE, set it
> > to
> > > > FALSE
> > > >
> > > >
> > > > By the way, another question for the rest of us, is there an easy way
> > to
> > > > convert the openldap schema's to apachds (is it enough to convert
> them
> > > and
> > > > add them under ou=schema?)
> > > >
> > > > what I want is to take the file of an openldap schema and just
> ldap-add
> > > > some
> > > > converted stuff to apache on the commandline, is there such a
> > converter?
> > > >
> > > >
> > > >
> > > > On Thu, May 8, 2008 at 3:20 PM, Pierre Smits <pierre.smits@gmail.com
> >
> > > > wrote:
> > > >
> > > > > I am testing the 1.5.2 windows version.
> > > > >
> > > > > When accessing the running ds service with apache studio I see the
> > > samba
> > > > > schema. However, when creating new entries I cannot select samba
> > > objects.
> > > > >
> > > > > How do I make the samba schema available in the list of selectable
> > > > > objects?
> > > > > Do I need to configure something?
> > > > >
> > > > >
> > > > > Regards,
> > > > >
> > > > > Pierre
> > > > >
> > > >
> > >
> >
>

Re: adding schema

Posted by Pierre Smits <pi...@gmail.com>.
The verion I am using is apacheds 1.5.2 with jvm 1.5.

It happened both on the linux and the windows version.

On Thu, May 8, 2008 at 11:40 PM, Alex Karasulu <ak...@apache.org> wrote:

> Give me some information to go on: platform, jvm, and ApacheDS version.
> Also turn on debugging after clearing out the log file and send it over.
>
> Alex
>
> On Thu, May 8, 2008 at 11:19 AM, Pierre Smits <pi...@gmail.com>
> wrote:
>
> > When enabling the samba schema via above mentioned method and restarting
> > the
> > server again, I get following error message:
> >
> >
> > Error while opening connection
> > [LDAP: error code 80 - failed on search operation: attributeType w/ OID
> > 1.3.6.1.1.1.1.0 not registered!]
> >  [LDAP: error code 80 - failed on search operation: attributeType w/ OID
> > 1.3.6.1.1.1.1.0 not registered!]
> >  Error occurred while loading schema, using default schema
> >
> > How do I correct this?
> >
> > Regards,
> >
> > Pierre
> >
> >
> > On Thu, May 8, 2008 at 3:28 PM, Jeroen Vriesman <linuxificator@gmail.com
> >
> > wrote:
> >
> > > I had the same problem some time ago,
> > >
> > > under cn=admin,ou=shema you can see that "m-disabled" is TRUE, set it
> to
> > > FALSE
> > >
> > >
> > > By the way, another question for the rest of us, is there an easy way
> to
> > > convert the openldap schema's to apachds (is it enough to convert them
> > and
> > > add them under ou=schema?)
> > >
> > > what I want is to take the file of an openldap schema and just ldap-add
> > > some
> > > converted stuff to apache on the commandline, is there such a
> converter?
> > >
> > >
> > >
> > > On Thu, May 8, 2008 at 3:20 PM, Pierre Smits <pi...@gmail.com>
> > > wrote:
> > >
> > > > I am testing the 1.5.2 windows version.
> > > >
> > > > When accessing the running ds service with apache studio I see the
> > samba
> > > > schema. However, when creating new entries I cannot select samba
> > objects.
> > > >
> > > > How do I make the samba schema available in the list of selectable
> > > > objects?
> > > > Do I need to configure something?
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Pierre
> > > >
> > >
> >
>

Re: adding schema

Posted by Pierre Smits <pi...@gmail.com>.
How do I turn debugging on?


On Thu, May 8, 2008 at 11:40 PM, Alex Karasulu <ak...@apache.org> wrote:

> Give me some information to go on: platform, jvm, and ApacheDS version.
> Also turn on debugging after clearing out the log file and send it over.
>
> Alex
>

Re: adding schema

Posted by Alex Karasulu <ak...@apache.org>.
Give me some information to go on: platform, jvm, and ApacheDS version.
Also turn on debugging after clearing out the log file and send it over.

Alex

On Thu, May 8, 2008 at 11:19 AM, Pierre Smits <pi...@gmail.com>
wrote:

> When enabling the samba schema via above mentioned method and restarting
> the
> server again, I get following error message:
>
>
> Error while opening connection
> [LDAP: error code 80 - failed on search operation: attributeType w/ OID
> 1.3.6.1.1.1.1.0 not registered!]
>  [LDAP: error code 80 - failed on search operation: attributeType w/ OID
> 1.3.6.1.1.1.1.0 not registered!]
>  Error occurred while loading schema, using default schema
>
> How do I correct this?
>
> Regards,
>
> Pierre
>
>
> On Thu, May 8, 2008 at 3:28 PM, Jeroen Vriesman <li...@gmail.com>
> wrote:
>
> > I had the same problem some time ago,
> >
> > under cn=admin,ou=shema you can see that "m-disabled" is TRUE, set it to
> > FALSE
> >
> >
> > By the way, another question for the rest of us, is there an easy way to
> > convert the openldap schema's to apachds (is it enough to convert them
> and
> > add them under ou=schema?)
> >
> > what I want is to take the file of an openldap schema and just ldap-add
> > some
> > converted stuff to apache on the commandline, is there such a converter?
> >
> >
> >
> > On Thu, May 8, 2008 at 3:20 PM, Pierre Smits <pi...@gmail.com>
> > wrote:
> >
> > > I am testing the 1.5.2 windows version.
> > >
> > > When accessing the running ds service with apache studio I see the
> samba
> > > schema. However, when creating new entries I cannot select samba
> objects.
> > >
> > > How do I make the samba schema available in the list of selectable
> > > objects?
> > > Do I need to configure something?
> > >
> > >
> > > Regards,
> > >
> > > Pierre
> > >
> >
>

Re: adding schema

Posted by Pierre Smits <pi...@gmail.com>.
When enabling the samba schema via above mentioned method and restarting the
server again, I get following error message:


Error while opening connection
[LDAP: error code 80 - failed on search operation: attributeType w/ OID
1.3.6.1.1.1.1.0 not registered!]
  [LDAP: error code 80 - failed on search operation: attributeType w/ OID
1.3.6.1.1.1.1.0 not registered!]
  Error occurred while loading schema, using default schema

How do I correct this?

Regards,

Pierre


On Thu, May 8, 2008 at 3:28 PM, Jeroen Vriesman <li...@gmail.com>
wrote:

> I had the same problem some time ago,
>
> under cn=admin,ou=shema you can see that "m-disabled" is TRUE, set it to
> FALSE
>
>
> By the way, another question for the rest of us, is there an easy way to
> convert the openldap schema's to apachds (is it enough to convert them and
> add them under ou=schema?)
>
> what I want is to take the file of an openldap schema and just ldap-add
> some
> converted stuff to apache on the commandline, is there such a converter?
>
>
>
> On Thu, May 8, 2008 at 3:20 PM, Pierre Smits <pi...@gmail.com>
> wrote:
>
> > I am testing the 1.5.2 windows version.
> >
> > When accessing the running ds service with apache studio I see the samba
> > schema. However, when creating new entries I cannot select samba objects.
> >
> > How do I make the samba schema available in the list of selectable
> > objects?
> > Do I need to configure something?
> >
> >
> > Regards,
> >
> > Pierre
> >
>

Re: adding schema

Posted by Emmanuel Lecharny <el...@apache.org>.
Alex Karasulu wrote:
> On Thu, May 8, 2008 at 9:28 AM, Jeroen Vriesman <li...@gmail.com>
> wrote:
>
>   
>> By the way, another question for the rest of us, is there an easy way to
>> convert the openldap schema's to apachds (is it enough to convert them and
>> add them under ou=schema?)
>>
>> what I want is to take the file of an openldap schema and just ldap-add
>> some
>> converted stuff to apache on the commandline, is there such a converter?
>>
>>     
>
> Not at this point.  I think we have some code around that can do something
> like this but there is no CLI tool.  Studio might do it but would want one
> of those folks to answer definitively.
>   
There is some converter which transform the schema to a ldif file, which 
has to be send to the server. I think that Studio allows you to do that.

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



Re: adding schema

Posted by Alex Karasulu <ak...@apache.org>.
Anyone is welcome to relax this in the parser.

Alex

On Fri, May 9, 2008 at 4:48 PM, Emmanuel Lecharny <el...@apache.org>
wrote:

> Jeroen Vriesman wrote:
>
>> Ok, I can import now,
>>
>> I also noticed that importing:
>> objectclass ( 1.3.6.1.4.1.17416.0.255.0.14 NAME 'hivosMailAccount' SUP top
>> AUXILIARY
>>        DESC 'Mail account object as used by Hivos'
>>        MUST ( mail $ homeDirectory $ mailbox $ userPassword )
>>        MAY ( quota $ subscribeToSharedFolder $ isSharedFolder $ hivosIsIn
>> $
>> horoAanwezig $ horoInDienst $ horoThuis ) )
>>
>> Did not work, it compained about the DESC line, to make it work I had to
>> change it to:
>> objectclass ( 1.3.6.1.4.1.17416.0.255.0.14
>>        NAME 'hivosMailAccount'
>>        DESC 'Mail account object as used by Hivos'
>>        SUP top AUXILIARY
>>        MUST ( mail $ homeDirectory $ mailbox $ userPassword )
>>        MAY ( quota $ subscribeToSharedFolder $ isSharedFolder $ hivosIsIn
>> $
>> horoAanwezig $ horoInDienst $ horoThuis ) )
>>
>> It seems to be very strich about the order, is this also in the protocol
>> specification?
>>
>>
> This is not in the protocol spec, but this is in RFC 4512, par. 4.1.1  :
>
>    ObjectClassDescription = LPAREN WSP
>        numericoid                 ; object identifier
>        [ SP "NAME" SP qdescrs ]   ; short names (descriptors)
>        [ SP "DESC" SP qdstring ]  ; description
>        [ SP "OBSOLETE" ]          ; not active
>        [ SP "SUP" SP oids ]       ; superior object classes
>        [ SP kind ]                ; kind of class
>        [ SP "*MUST*" SP oids ]      ; attribute types
>        [ SP "*MAY*" SP oids ]       ; attribute types
>        extensions WSP RPAREN
>
> A little bit strict, if you want my opinion...
>
> --
> --
> cordialement, regards,
> Emmanuel Lécharny
> www.iktek.com
> directory.apache.org
>
>
>

Re: adding schema

Posted by Emmanuel Lecharny <el...@apache.org>.
Jeroen Vriesman wrote:
> Ok, I can import now,
>
> I also noticed that importing:
> objectclass ( 1.3.6.1.4.1.17416.0.255.0.14 NAME 'hivosMailAccount' SUP top
> AUXILIARY
>         DESC 'Mail account object as used by Hivos'
>         MUST ( mail $ homeDirectory $ mailbox $ userPassword )
>         MAY ( quota $ subscribeToSharedFolder $ isSharedFolder $ hivosIsIn $
> horoAanwezig $ horoInDienst $ horoThuis ) )
>
> Did not work, it compained about the DESC line, to make it work I had to
> change it to:
> objectclass ( 1.3.6.1.4.1.17416.0.255.0.14
>         NAME 'hivosMailAccount'
>         DESC 'Mail account object as used by Hivos'
>         SUP top AUXILIARY
>         MUST ( mail $ homeDirectory $ mailbox $ userPassword )
>         MAY ( quota $ subscribeToSharedFolder $ isSharedFolder $ hivosIsIn $
> horoAanwezig $ horoInDienst $ horoThuis ) )
>
> It seems to be very strich about the order, is this also in the protocol
> specification?
>   
This is not in the protocol spec, but this is in RFC 4512, par. 4.1.1  :

     ObjectClassDescription = LPAREN WSP
         numericoid                 ; object identifier
         [ SP "NAME" SP qdescrs ]   ; short names (descriptors)
         [ SP "DESC" SP qdstring ]  ; description
         [ SP "OBSOLETE" ]          ; not active
         [ SP "SUP" SP oids ]       ; superior object classes
         [ SP kind ]                ; kind of class
         [ SP "*MUST*" SP oids ]      ; attribute types
         [ SP "*MAY*" SP oids ]       ; attribute types
         extensions WSP RPAREN

A little bit strict, if you want my opinion...

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



Re: adding schema

Posted by Jeroen Vriesman <li...@gmail.com>.
Ok, I can import now,

I also noticed that importing:
objectclass ( 1.3.6.1.4.1.17416.0.255.0.14 NAME 'hivosMailAccount' SUP top
AUXILIARY
        DESC 'Mail account object as used by Hivos'
        MUST ( mail $ homeDirectory $ mailbox $ userPassword )
        MAY ( quota $ subscribeToSharedFolder $ isSharedFolder $ hivosIsIn $
horoAanwezig $ horoInDienst $ horoThuis ) )

Did not work, it compained about the DESC line, to make it work I had to
change it to:
objectclass ( 1.3.6.1.4.1.17416.0.255.0.14
        NAME 'hivosMailAccount'
        DESC 'Mail account object as used by Hivos'
        SUP top AUXILIARY
        MUST ( mail $ homeDirectory $ mailbox $ userPassword )
        MAY ( quota $ subscribeToSharedFolder $ isSharedFolder $ hivosIsIn $
horoAanwezig $ horoInDienst $ horoThuis ) )

It seems to be very strich about the order, is this also in the protocol
specification?

Regards,
Jeroen.


On Fri, May 9, 2008 at 11:35 AM, Alex Karasulu <ak...@apache.org> wrote:

> Lowercase the objectClass to objectclass.  Same with attributeType make
> sure
> 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 <li...@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
> care
> > 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
> top
> > 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 <el...@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
> drop
> > > 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
> request
> > 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écharny
> > > www.iktek.com
> > > directory.apache.org
> > >
> > >
> > >
> >
>

Re: adding schema

Posted by Alex Karasulu <ak...@apache.org>.
Lowercase the objectClass to objectclass.  Same with attributeType make sure
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 <li...@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 care
> 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 top
> 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 <el...@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 drop
> > 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 request
> 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écharny
> > www.iktek.com
> > directory.apache.org
> >
> >
> >
>

Re: adding schema

Posted by Jeroen Vriesman <li...@gmail.com>.
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 care
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 top
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 <el...@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 drop
> 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 request 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écharny
> www.iktek.com
> directory.apache.org
>
>
>

Re: adding schema

Posted by Emmanuel Lecharny <el...@apache.org>.
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 
drop 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 request 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écharny
www.iktek.com
directory.apache.org



Re: adding schema

Posted by Stefan Seelmann <se...@apache.org>.
Hi Jeroen,
> I tried it with studio,
> 
> didn't work, 

why doesn't it work? Do you got an error?

The way to do is
- create a new schema project
- import schemas from OpenLDAP files
- export schema for ApacheDS

Here is the doc:
http://directory.apache.org/studio/static/users_guide/schema_editor/

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

Regards,
Stefan

Re: adding schema

Posted by Jeroen Vriesman <li...@gmail.com>.
I tried it with studio,

didn't work, 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.

I will try to put together a script to do this and post it here.

On Thu, May 8, 2008 at 4:00 PM, Alex Karasulu <ak...@apache.org> wrote:

> On Thu, May 8, 2008 at 9:28 AM, Jeroen Vriesman <li...@gmail.com>
> wrote:
>
> > By the way, another question for the rest of us, is there an easy way to
> > convert the openldap schema's to apachds (is it enough to convert them
> and
> > add them under ou=schema?)
> >
> > what I want is to take the file of an openldap schema and just ldap-add
> > some
> > converted stuff to apache on the commandline, is there such a converter?
> >
>
> Not at this point.  I think we have some code around that can do something
> like this but there is no CLI tool.  Studio might do it but would want one
> of those folks to answer definitively.
>
> Good idea tho to add this to the apacheds-tools as a command (that works
> :)
> ).
>
> Alex
>

Re: adding schema

Posted by Alex Karasulu <ak...@apache.org>.
On Thu, May 8, 2008 at 9:28 AM, Jeroen Vriesman <li...@gmail.com>
wrote:

> By the way, another question for the rest of us, is there an easy way to
> convert the openldap schema's to apachds (is it enough to convert them and
> add them under ou=schema?)
>
> what I want is to take the file of an openldap schema and just ldap-add
> some
> converted stuff to apache on the commandline, is there such a converter?
>

Not at this point.  I think we have some code around that can do something
like this but there is no CLI tool.  Studio might do it but would want one
of those folks to answer definitively.

Good idea tho to add this to the apacheds-tools as a command (that works :)
).

Alex

Re: adding schema

Posted by Jeroen Vriesman <li...@gmail.com>.
I had the same problem some time ago,

under cn=admin,ou=shema you can see that "m-disabled" is TRUE, set it to
FALSE


By the way, another question for the rest of us, is there an easy way to
convert the openldap schema's to apachds (is it enough to convert them and
add them under ou=schema?)

what I want is to take the file of an openldap schema and just ldap-add some
converted stuff to apache on the commandline, is there such a converter?



On Thu, May 8, 2008 at 3:20 PM, Pierre Smits <pi...@gmail.com> wrote:

> I am testing the 1.5.2 windows version.
>
> When accessing the running ds service with apache studio I see the samba
> schema. However, when creating new entries I cannot select samba objects.
>
> How do I make the samba schema available in the list of selectable
> objects?
> Do I need to configure something?
>
>
> Regards,
>
> Pierre
>