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

Re: use-case for arg const char *dn of ldap_sasl_bind_s()

To: Michael Ströder <michael@stroeder.com>, OpenLDAP Technical <openldap-technical@OpenLDAP.org>
Subject: Re: use-case for arg const char *dn of ldap_sasl_bind_s()
From: Howard Chu <hyc@symas.com>
Date: Sun, 18 Aug 2019 17:35:22 +0100
In-reply-to: <128a75f7-027f-f1f1-7d8f-9e4bbef49567@stroeder.com>
References: <128a75f7-027f-f1f1-7d8f-9e4bbef49567@stroeder.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53

Michael Ströder wrote:
> HI!
> 
> It seems I've never passed a DN to SASL bind functions.
> 
> Could someone please elaborate on a valid use-case for argument dn of
> libldap function ldap_sasl_bind_s()?

I suppose it is only exposed since the protocol message still carries it,
even though it is always empty. The client could legally put anything it wants
in there; a proper server would still just ignore the DN though.
> 
> Thanks in advance.
> 
> Ciao, Michael.
> 
> 


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

Follow-Ups:
- Re: use-case for arg const char *dn of ldap_sasl_bind_s()
  - From: Michael Ströder <michael@stroeder.com>

References:
- use-case for arg const char *dn of ldap_sasl_bind_s()
  - From: Michael Ströder <michael@stroeder.com>

Prev by Date: use-case for arg const char *dn of ldap_sasl_bind_s()
Next by Date: Re: use-case for arg const char *dn of ldap_sasl_bind_s()
Index(es):
- Chronological
- Thread