Bug #59073 Make fastbind method available for MEM when using Microsoft AD LDAP
Submitted: 20 Dec 2010 22:16
Reporter: Roel Van de Paar Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S4 (Feature request)
Version: OS:Any
Assigned to: Mark Matthews CPU Architecture:Any

[20 Dec 2010 22:16] Roel Van de Paar 
Description:
Add ad-specific fastbind method to the code for comparison mode in MEM when using AD LDAP.

How to repeat:
Currently it is not possible to use comparison mode with AD LDAP for MEM. Reason is that Microsoft AD LDAP does not make the password field(s) readable. 

Suggested fix:
There was a prior bug in which comparison mode was incorrectly linked with a non-anon bind user/pass prior to 2.3.1 (bug #58132). This should now have been split out since 2.3.1. Now the fastbind method has to be added so comparison mode can work with AD LDAP specifically.
[20 Dec 2010 22:52] Roel Van de Paar 
Changed synopsis to match further discussion: fastbind will be available "generally" for Microsoft AD LDAP. Unrelated to comparison mode.
[20 Dec 2010 23:07] Roel Van de Paar 
(Fastbind is simply an "optimization" of a non-anonymous bind. Fastbind gives a cut-down view of the AD schema rather than trying to read the whole tree.)