On 8/18/19 6:35 PM, Howard Chu wrote: > Michael Ströder wrote: >> 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. Understood. I assume the same applies to parameter who of ldap_sasl_interactive_bind_s(). Ciao, Michael.
