Print

The latest release information for the Active Directory module.

1.  Release History

December 26 , 2014

Sitecore Active Directory v1.2 is released.

Tested with Sitecore CMS 7.2 rev. 141124 (Update-3), Sitecore CMS 7.5 rev. 141217 and Sitecore XP 8.0 rev. 141212.

Compatibility 
This version of the module only runs on Sitecore 7.2 or later.

Change log.

Issues resolved:

• The LDAPLogin page did not register the user ticket. The issue has been fixed. (TFS 864)
• Single sign-on through the module negatively impacted the Experience Editor ribbon (in preview mode). The issue has been fixed. (TFS 822)
• Spaces in the Organization Unit name were not supported. The issue has been fixed. (TFS 861)
• AD used the same cache for the same connection string, but with different organizations. The issue has been fixed. (TFS 12526)
• The SitecoreADMembershipProvider created users with incorrect password question/answer values. The issue has been fixed. (TFS 868)
• The attributeMapName="sAMAccountName" intermittently caused the DirectoryNotificationProvider to stop working. The issue has been fixed. (TFS 12527)
• The SitecoreADRoleProvider returned no roles if the Role's cache was disabled. The issue has been fixed. (TFS 12893)

2.  Known issues

The list of known issues which are present in the current version of the Active Directory module.

1. When the AD server name starts with “dc” or “DC” in the AD connection string, as in:
   
   <add name="ManagersConnString" connectionString="LDAP://dctest/DC=company,DC=net "/>
   the AD module writes errors to the log file:
   1320 12:18:00 WARN AD: reconnected
   1320 12:18:00 WARN AD : attempt reconnecting...
   Workaround:
   Use the server IP instead of the server name in the AD connection string:
   
   <add name="ManagersConnString" connectionString="LDAP://[IP]/DC=company,DC=net "/>
   [IP] is the IP of the AD server, e.g. 127.0.0.1
   The AD connection string is placed in the App_Config/ConnectionStrings.config file.
2. The AD module does not support the SSL protocol.
3. ActiveDirectoryMembershipUser doesn't support LastLoginDate and LastActivityDate and there are no default properties in AD. 
   http://msdn.microsoft.com/ru-ru/library/system.web.security.activedirectorymembershipuser.lastlogindate%28v=vs.110%29.html