[Date Prev][Date Next]
Re: managing OpenLDAP / back-config
- To: Hallvard B Furuseth <firstname.lastname@example.org>
- Subject: Re: managing OpenLDAP / back-config
- From: Michael Ströder <email@example.com>
- Date: Tue, 17 Jun 2008 19:47:42 +0200
- Cc: openldap-software@OpenLDAP.org
- In-reply-to: <firstname.lastname@example.org>
- References: <email@example.com> <478C6E31.firstname.lastname@example.org> <email@example.com> <478DDAE5.firstname.lastname@example.org> <48578E58.email@example.com> <firstname.lastname@example.org>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/20080313 SeaMonkey/1.1.9
Hallvard B Furuseth wrote:
Michael Ströder writes:
Since web2ldap and the delta-modification generator has full schema
knowledge today I could look up whether there's an EQUALITY matching
rule defined for a given attribute type and then explicitly delete
certain attribute values like Hallvard suggested.
Actually I wasn't suggesting that for web2ldap, though it sounds nice.
At the time I was talking about how EQUALITY rules would make it easier
to write config LDIFs by hand.
I've now implemented that. Needs testing with other LDAP server
implementations as well and many weird attribute types. The main problem
with such an approach is that subschema is always incomplete. :-(