1. Release History

November 30, 2006

LDAP v6.0.3.5 is released.

Changes:

Fixed: Log in to Windows as a user who cannot be automatically logged into the client. Request <your hostname>/login. The user ends up with the HTTP Bad Request error.

LDAP version 6.0.3.4 is released.

Changes:

Fixed: Users or Groups with a dash ('–') in their name in your directory cannot be replicated into Sitecore.

LDAP version 6.0.3.3 is released.

Note: version 6.0.3.3 is the latest version, it replaces version 6.2.3.

Changes:

Fixed: Search of users and groups causes an error when the language of the "modules_shell" isn’t English.
Fixed: Extranet user is unable to login directly when language of the site is other than English.

LDAP version 6.2.3 is released. This is the first release of the module for Sitecore 5.2.

Changes:

When you add a group using the LDAPmodule, the following will be written in the log - 3404 16:34:15 WARN The path "/sitecore/system/languages" was not found.
Warning entries appear in the Log file when you add a User or a group with LDAP application. For instance:
5532 18:24:44 WARN Could not resolve security item (AKLDAPgroup). Key: akldapgroup{A7DF04B4-4C4B-44B7-BE1E-AD901BD53DAD}
5532 18:24:44 WARN Could not resolve security item (alko). Key: alko{642C9A7E-EE31-4979-86F0-39F338C10AFB}
It’s not possible for an added User that has the “Password must be changed at next logon” option set in your directory to login to Sitecore (this only concerns the Live Validation and Mixed modes).
v6.0.0 issue: In the Mixed mode, the module allows an added User to login only if one of the groups, which he belongs to, is already added. Otherwise, an empty page with an error string appears.
Currently, the module comes in the English language version only.
The Full name radio button can be selected, but appears as disabled.
The Add Groupsmembers setting (System » Modules » LDAP » LDAPclient/extranet) duplicates the Add Groupmembers checkbox in the LDAP application.
After successful or unsuccessful login to Sitecore via the <your hostname>/Sitecore link, added groups cannot be deleted from Sitecore security by LDAP module.
If you change the mode from "Live" to "Mixed", you must delete all ldap temporary users from the sitecore/users/temporary folder in Sitecore and Extranet databases.

The module cannot register user primary groups in Active Directory.
It is required that your directory users contain a property informing which group the User is a member of – is default in AD and eDir; however, it can be a problem if you’re running in a Notes/Domino environment.
When a User tries to login to Sitecore, only valid direct memberships are registered, not the transitive (nested) ones.
The update for added fields works properly only if the LDAP field name, the value of the field’s Title property and the name of the field in the Security templates.xml file are identical.
Sitecore LDAP module does not support working across domains.