diff options
author | Günther Deschner <gd@samba.org> | 2005-10-21 12:50:39 +0000 |
---|---|---|
committer | Gerald (Jerry) Carter <jerry@samba.org> | 2007-10-10 11:05:09 -0500 |
commit | 0698148b44aeb471137b2f516f09fb9653085511 (patch) | |
tree | 883b9c1c4ee307010d90ebb6a1b185bb84eed843 /source3/torture | |
parent | cd310c19cefddc799ec5f8b374bc9c5ea9dec5f1 (diff) | |
download | samba-0698148b44aeb471137b2f516f09fb9653085511.tar.gz samba-0698148b44aeb471137b2f516f09fb9653085511.tar.bz2 samba-0698148b44aeb471137b2f516f09fb9653085511.zip |
r11242: use LDAP bitwise machting rule when searching for groups in ADS.
This avoids that each time a full-group-dump is requested from ADS; the
bitwise match allows to only query those groups we are interested in.
The ADS LDAP server changed to RFC compliant behaviour when decoding the ldap
filter with extensible match in the latest SPs (fixes). From the patch:
/* Workaround ADS LDAP bug present in MS W2K3 SP0 and W2K SP4 w/o
* rollup-fixes:
*
* According to Section 5.1(4) of RFC 2251 if a value of a type is it's
* default value, it MUST be absent. In case of extensible matching the
* "dnattr" boolean defaults to FALSE and so it must be only be present
* when set to TRUE.
*
* When it is set to FALSE and the OpenLDAP lib (correctly) encodes a
* filter using bitwise matching rule then a buggy AD fails to decode
* the extensible match. As a workaround set it to TRUE and thereby add
* the dnAttributes "dn" field to cope with those older AD versions.
* It should not harm and won't put any additional load on the AD since
* none of the dn components have a bitmask-attribute.
*
* Thanks to Ralf Haferkamp for input and testing */
Guenther
(This used to be commit db38ed6be607d08515920d46fb8a12f8cb4ddd6e)
Diffstat (limited to 'source3/torture')
0 files changed, 0 insertions, 0 deletions