Products.ldapuserfolder

---------------------
- Not only did the importing semantics for the latest
python-ldap modules change, some fundamental method
signatures changed as well. This fixes the call to
ldap.open which led to uncontrollable debugging
output on the command line since 1.2beta2 (Tracker
issue 106 - thanks to David Rideau).

---------------------
- Ensure compatibility with the latest python-ldap releases
which introduced an underdocumented and spurious change
that mandates a different way of importing the ldap
module. (Tracker issues 102 and 105)
The recommended python-ldap module to use remains
1.10alpha3 which seems to work more reliably and has
less bugs.

---------------------
- If the authentication information was incorrect, the
_searchResults method would raise the Unauthorized
exception, which would make basic HTTP authentication boxes
pop up even in cookie mode. It now returns an empty string
and users will get the login page when in cookie mode.
Tracker issue 87 - thanks to Eric Brun.
- Some browsers would not display the LDAP server port in the
configuration tab due to a line break in the DTML for the
form. The line break has been removed. (Tracker issue 103,
thanks once again to Florent Guillaume)
- A little more extended debug logging in the _lookupuser
method (suggested by Marc-Aurele Darche of IDEALX, Tracker
issue 101)
- The RDN Attribute dropdown in the Configure tab now lists
all attributes defined on the LDAP Schema tab. This allows
the administrator to select any attribute if the LDAP setup
violates RFC 2377. Suggestion and patch (thanks!) from
Marc-Aurele Darche of IDEALX, Tracker issue 101.

----------------
- Exclusively use direct string method invocation as opposed
to using the string module
- Mistakenly cached the superuser account upon successful
authentication. This would break the "Caches" tab because
it tries to call a method on each cached user object that
is not supported by the superuser API.
- A spurious "/" in the "Add Object" widget of the "Contents"
tab broke rendering of the dropdown list in some browsers.
- Updated all help screens, some were outdated
- Updated the API help files

---------------------
- Typo inside the method that adds user records led to an
obscure error message and user roles would not be set
(Tracker issue 95, submitted by M. A. Darche if IDEALX)
- The targets of some MessageDialog error screens for the
management interface pointed to the wrong method name
and caused a traceback.

---------------------
- The administrator can now choose between reading group
information from the LDAP server or storing it inside
the LDAP User Folder itself. This feature has been added
in response to Tracker issue 94. Thanks go to Colin Smith
for bringing this configuration option to my attention.
- The Users tab in the ZMI would show tracebacks if the
connection to the LDAP server produced an error. Now the
real error is shown (Tracker Issue 93)
- Some details of the ZBabel transition did not work
correctly, in particular the add screen blew up.