[Date Prev][Date Next]
Re: Problem with searches transgressing suffixmassage-d suffix
On 6/26/06, Buchan Milne <email@example.com> wrote:
We have a weird legacy DIT which is going to be migrated to a new more
organised structure by an ongoing project.
In the meantime, we are deploying provisioning tools which we would prefer not
to modify at the time of the migration.
So, back-relay seems to be the obvious solution (provision to the final
structure, rewrite with back-relay into the old structure).
So, I have added a new database on one of our dev servers:
relay cn=webmail,ou=mail,dc=isp massage
There is a bdb database that holds cn=mail,ou=isp (the legacy basedn).
That works great, searches on cn=webmail,cn=mail,ou=isp returns an entry I
added under cn=webmail,ou=mail,dc=isp ... except that the first search on the
cn=mail,ou=isp suffix kills the relay. Any other search which should find
anything under cn=webmail,cn=mail,ou=isp returns error 32.
I've also tried replacing the relay database with a configurations
using "database meta" and "database ldap" with rwm-suffixmassage, and they do
the same thing.
It seems I must be missing something here ...
I have also setup something similar (although I'm attribute mapping),
and I don't see your problems.
Here's how mine is setup:
index objectClass eq
map attribute homeDirectory testSolarisHomeDirectory
map attribute homeDirectory testLinuxHomeDirectory
I do end up with two homeDirectory attributes coming back if I search
for all attributes, but searches specifically for homeDirectory return
my test*HomeDirectory stuff.