Re: (ITS#4487) Problem with dereferencing aliases to remote DB with different suffix

[hyc@symas.com]

Quanah Gibson-Mount wrote:
>
>
> --On Tuesday, April 11, 2006 5:49 PM -0700 Howard Chu <hyc@symas.com> 
> wrote:
>
>> quanah@stanford.edu wrote:
>>> --On Tuesday, April 11, 2006 9:42 PM +0000 skoulik@gmail.com wrote:
>>>
>>>> Expected result: alias entry is transparently dereferenced into
>>>> cn=Person1,ou=target2,dc=my-domain,dc=com data
>>>>
>>>> Actual result: search returns no results
>>>>
>>>> PS:
>>>> Don't hesitate to contact me if you need additional information.
>>>>
>>>
>>> I will note that back-meta underwent a large bit of rewriting between
>>> 2.3.20 and 2.3.21, so it is possible that the issue you are seeing is
>>> fixed.
>>>
>>>
>> Irrelevant. Aliases are not the same as referrals. Aliases can only 
>> point
>> to other entries within the same database, you must use referrals to
>> point to something in a different database.
>
> I didn't say anything about referrals... I just noted large parts of 
> back-meta had been rewritten.
>
Right, you didn't mention referrals, but you should have. The fact is 
that referrals are the only kind of reference that works across foreign 
databases. Aliases aren't designed for that; the fact that dereferencing 
them across remote DBs doesn't work is inherent in the directory model.

-- 
  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc
  OpenLDAP Core Team            http://www.openldap.org/project/