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

Re: Re-investigating ppolicy + chain issues on a consumer: chain configuration

To: openldap-technical@openldap.org
Subject: Re: Re-investigating ppolicy + chain issues on a consumer: chain configuration
From: "Dieter Kluenter" <dieter@dkluenter.de>
Date: Thu, 24 Jun 2010 08:07:48 +0200
In-reply-to: <78FC5CC7782A4643B6F08716A021FA302945DE3C@IT-EXMB-01.silverspringnet.com> (Siddhartha Jain's message of "Wed, 23 Jun 2010 18:18:29 -0700")
References: <78FC5CC7782A4643B6F08716A021FA302945DE3C@IT-EXMB-01.silverspringnet.com>
User-agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.5-b29 (linux)

Siddhartha Jain <sjain@silverspringnet.com> writes:

> I am still stuck at the same place where a chained consumer allows a
> client to auth with a bad password. Remove chaining and bad passwords
> are no longer accepted.
>
> To troubleshoot from scratch, I am curious about how chaining should
> be configured in the new ldif-based configuration scheme?
[...]
> Interestingly, it creates two "ldap" databases for a single "chain"
> overlay. Can someone please explain why/how is this so? Why does
> chaining go to "frontend" db instead of being under the database that
> is chained? I tried to create the "ldap" databases under a "bdb"
> database but OpenLDAP won't allow that.

Two databases are created because chain in principle is a ldap backend
plus additonal chaining configuration options.

-Dieter

-- 
Dieter Klünter | Systemberatung
sip: +49.40.20932173
http://www.dpunkt.de/buecher/2104.html
GPG Key ID:8EF7B6C6

References:
- Re-investigating ppolicy + chain issues on a consumer: chain configuration
  - From: Siddhartha Jain <sjain@silverspringnet.com>

Prev by Date: Re: Textual LDIF backup strategies for busy LDAP clusters
Next by Date: Unique Overlay Help
Index(es):
- Chronological
- Thread