Issue 7864 - slapo-translucent should honour the manageDSAit control
Summary: slapo-translucent should honour the manageDSAit control
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: 2.4.39
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-29 10:38 UTC by jkozyra@gmail.com
Modified: 2014-10-23 07:31 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description jkozyra@gmail.com 2014-05-29 10:38:47 UTC
Full_Name: Jillian Kozyra
Version: 2.4.39
OS: 
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (78.155.234.81)


ManageDSAit is honoured by other overlays like dynlist, retcode, and unique. The
translucent overlay should add this functionality.
Comment 1 Quanah Gibson-Mount 2014-05-29 11:07:03 UTC
changed notes
changed state Open to Release
moved from Incoming to Software Bugs
Comment 2 Michael Ströder 2014-05-29 13:27:48 UTC
jkozyra@gmail.com wrote:
> ManageDSAit is honoured by other overlays like dynlist, retcode, and unique. The
> translucent overlay should add this functionality.

Can your please elaborate on the semantics you want to have when using
ManageDSAit control.

Originally ManageDSAit control was only meant to manage referral entries.

It was (ab)used for some other purposes especially *before* Relax Rules
control was defined/implemented.

Ciao, Michael.

Comment 3 Howard Chu 2014-05-29 13:42:56 UTC
michael@stroeder.com wrote:
> This is a cryptographically signed message in MIME format.

> jkozyra@gmail.com wrote:
>> ManageDSAit is honoured by other overlays like dynlist, retcode, and un=
> ique. The
>> translucent overlay should add this functionality.
>
> Can your please elaborate on the semantics you want to have when using
> ManageDSAit control.
>
> Originally ManageDSAit control was only meant to manage referral entries.=

> It was (ab)used for some other purposes especially *before* Relax Rules
> control was defined/implemented.

In particular, the control changes search behavior to return the actual entry 
for a referral entry, instead of returning a searchReference. In the other 
overlays, e.g. dynlist, the control changes search behavior to return the 
actual entry, instead of trying to expand the list of dynamic members.

For translucent, the control should return the actual local entry, instead of 
trying to return the result of merging local and remote data.

The use case is the same as for the other overlays - make sure we get actual 
entries as they are stored in the server, as opposed to some dynamically 
transformed version of the entries.

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

Comment 4 Michael Ströder 2014-05-29 13:53:39 UTC
hyc@symas.com wrote:
> michael@stroeder.com wrote:
>> This is a cryptographically signed message in MIME format.
> 
>> jkozyra@gmail.com wrote:
>>> ManageDSAit is honoured by other overlays like dynlist, retcode, and un=
>> ique. The
>>> translucent overlay should add this functionality.
>>
>> Can your please elaborate on the semantics you want to have when using
>> ManageDSAit control.
>>
>> Originally ManageDSAit control was only meant to manage referral entries.=
> 
>> It was (ab)used for some other purposes especially *before* Relax Rules
>> control was defined/implemented.
> 
> In particular, the control changes search behavior to return the actual entry 
> for a referral entry, instead of returning a searchReference. In the other 
> overlays, e.g. dynlist, the control changes search behavior to return the 
> actual entry, instead of trying to expand the list of dynamic members.
> 
> For translucent, the control should return the actual local entry, instead of 
> trying to return the result of merging local and remote data.

I thought the Proxy cache privateDB control (1.3.6.1.4.1.4203.666.11.9.5.1)
should be used for that.

CIao, Michael.

Comment 5 OpenLDAP project 2014-10-23 07:31:31 UTC
fixed in master
fixed in RE24
fixed in RE25
Comment 6 Quanah Gibson-Mount 2014-10-23 07:31:31 UTC
changed notes
changed state Release to Closed