Description

This article describes the known issues with the Sitecore Active Directory (AD) module.

For information about the availability of the fixes for the mentioned known issues, refer to the Release Notes of the future AD releases.

Known Issues For Active Directory 1.4

• The AD module does not work in conjunction with Federated Authentication. When you use Sitecore XP with the Federated Authentication configuration enabled, you must not use the AD module.
• The AD module does not support the SSL protocol.
• The first installation of the module package can fail without any exact error description.
  Workaround: Install the package again (click the relevant button on the last wizard screen) and click the Overwrite option for all files.
• An exception can occur when changing the profile of an Active Directory user created in Sitecore XP.
  Workaround: Open the \App_Config\Security\Domains.config.xml file and add the following line to the domains element:

  <domain name="ad" ensureAnonymousUser="false" defaultProfileItemID="{DDEDA46F-169B-4A70-8732-DBD3F407AF2E}"/>

  The defaultProfileItemID attribute defines the profile item that is used for users from the domain if the profile is not set for the user explicitly.​
• When the AD server name starts with "dc" or "DC" in the AD connection string, for example:

   <add name="ManagersConnString" connectionString="LDAP://dctest/DC=company,DC=net "/>

  the AD module writes the following warnings to the log file:

  12:18:00 WARN AD: reconnected
  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 address of the AD server, for example, 127.0.0.1. The AD connection string is defined in the \App_Config\ConnectionStrings.config file.
• If you have written custom code that calls the Active Directory module's API, you can encounter compilation errors (for example, missing assembly) when you upgrade to the latest version. This can be caused by a change in the assembly version between the previous and latest module versions.
  Workaround: Re-reference the module assembly as a version independent reference (specific version = "false") and recompile your code.