[Date Prev][Date Next]
RE: LDAPS (LDAP over SSL) client authentication
> An LDAPv3 simple Bind request or an LDAPv2 simple Bind with a
> non-zero-length name or password causes the server to ignore the SSL
> 'Client Certificate'; the subsequent authorization identity is either
> anonymous or the name given in the Bind request. A client may resume
What about doing a SASL bind with a mechanism other than EXTERNAL, over SSL?
Can I use that to set an alternate authorization identity too?