[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: unable to access schema via LDAP

To: "Wouter Mignon" <wouter.mignon@khleuven.be>
Subject: Re: unable to access schema via LDAP
From: "Pierangelo Masarati" <ando@sys-net.it>
Date: Tue, 31 Aug 2004 14:10:48 +0200 (CEST)
Cc: ando@sys-net.it, openldap-software@OpenLDAP.org
Importance: Normal
In-reply-to: <1093953603.4007.35.camel@sen>
References: <1093950627.4007.21.camel@sen> <36462.131.175.154.56.1093952603.squirrel@131.175.154.56> <36467.131.175.154.56.1093952762.squirrel@131.175.154.56> <1093953603.4007.35.camel@sen>
User-agent: SquirrelMail/1.4.3a-1

>> >
>> > 2) Fix slapd:
>> >   2a) change the definition of the name of the schema entry; or
>>
>> This is quite easy: see "schemadn" in slapd.conf(5).
>
> If i add schemadn cn=schema to my slapd.conf, will this hurt my directory
> or other apps using LDAP?

No, as long as they use the "subschemaSubentry" attribute in the rootDSE
to locate the position of the schema.  Of course, applications like the
one you're using are likely to be intimately broken...

p.

-- 
Pierangelo Masarati
mailto:pierangelo.masarati@sys-net.it


    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497

References:
- unable to access schema via LDAP
  - From: Wouter Mignon <wouter.mignon@khleuven.be>
- Re: unable to access schema via LDAP
  - From: "Pierangelo Masarati" <ando@sys-net.it>
- Re: unable to access schema via LDAP
  - From: Wouter Mignon <wouter.mignon@khleuven.be>

Prev by Date: Re: unable to access schema via LDAP
Next by Date: 3 newbie questions : include new schema, ACL,
Index(es):
- Chronological
- Thread