The easiest way to find out is just to try it :-)
ldapsearch -LLL -o ldif-wrap=no -h localhost -p 38901 -x -D
"cn=directory manager" -w ... -b "dc=example,dc=com" uid=kwinters
objectclass description uid
dn: uid=kwinters,ou=People,dc=example,dc=com
objectclass: top
objectclass: person
object
On Thu, 2018-11-08 at 00:12 +0100, Michael Ströder wrote:
> On 11/7/18 11:22 PM, William Brown wrote:
> > On Sat, 2018-11-03 at 21:46 +0100, Michael Ströder wrote:
> > > I vaguely remember that 389-DS also implements deref search
> > > control
> > > [1].
> > >
> > > My question as a client develop
On 11/7/18 11:22 PM, William Brown wrote:
On Sat, 2018-11-03 at 21:46 +0100, Michael Ströder wrote:
I vaguely remember that 389-DS also implements deref search control
[1].
My question as a client developer:
How does 389-DS deal with reference attributes being absent?
I am assuming that you m
On Sat, 2018-11-03 at 21:46 +0100, Michael Ströder wrote:
> HI!
>
> I vaguely remember that 389-DS also implements deref search control
> [1].
>
> My question as a client developer:
> How does 389-DS deal with reference attributes being absent?
Mi Michael,
I am assuming that you mean a request
