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

Re: Rename attribute before return

To: Digant C Kasundra <digant@uta.edu>
Subject: Re: Rename attribute before return
From: Aaron Richton <richton@nbcs.rutgers.edu>
Date: Wed, 20 Jul 2005 15:42:41 -0400 (EDT)
Cc: Openldap-Software <openldap-software@OpenLDAP.org>
In-reply-to: <1121886556.32241.51.camel@localizer.uta.edu>
References: <1121811807.26012.46.camel@localizer.uta.edu> <Pine.SOL.4.58.0507191858160.26857@toolbox.rutgers.edu> <1121814836.26012.52.camel@localizer.uta.edu> <42DDF74E.8040709@sys-net.it> <42DE7142.9050209@symas.com> <42DE7341.3030802@sys-net.it> <1121886556.32241.51.camel@localizer.uta.edu>

You could use a relay database to do this:

database	relay
suffix		"ou=Cooked,dc=example,dc=com"
relay		"ou=Uncooked,dc=example,dc=com"
overlay 	rwm
[rwm-whatever you want to change]


Then you could tell Your Favorite Commercial Software basedn="ou=Cooked"
while telling OpenLDAP software that basedn="ou=Uncooked." I know you
mentioned 2.2. You probably could use back-ldap or back-meta to accomplish
similar; it won't be quite as elegant, but it might work.

Follow-Ups:
- Re: Rename attribute before return
  - From: Digant C Kasundra <digant@uta.edu>

References:
- Rename attribute before return
  - From: Digant C Kasundra <digant@uta.edu>
- Re: Rename attribute before return
  - From: Aaron Richton <richton@nbcs.rutgers.edu>
- Re: Rename attribute before return
  - From: Digant C Kasundra <digant@uta.edu>
- Re: Rename attribute before return
  - From: Pierangelo Masarati <ando@sys-net.it>
- Re: Rename attribute before return
  - From: Howard Chu <hyc@symas.com>
- Re: Rename attribute before return
  - From: Pierangelo Masarati <ando@sys-net.it>
- Re: Rename attribute before return
  - From: Digant C Kasundra <digant@uta.edu>

Prev by Date: Re: Rename attribute before return
Next by Date: Re: Rename attribute before return
Index(es):
- Chronological
- Thread