Author: Halfvares Mats, Teknikhuset AB.

Published: 2005-06-14

Applies to:
  • Content Studio ver. 4.0 build 1010 and later running on a members server in Active Directory

Type: How to

More information

In some network environments Content Studio has problems to identify the user's properties in Active Directory. By default Content Studio tries to read the user properties like full name from Active Directory by using the LDAP protocol. Content Studio tries to bind to the user using the user's SID (LDAP://samDOMAIN/<SID=xxxxxxxxxx>). If this fails Content Studio assumes that the server is a stand-alone server and tries the old WinNT protocol instead. In an AD the latter method often fails where LDAP succeeds and thus LDAP might be the only acceptably method. In order to check the nature of the LDAP error a new registry value was added in Content Studio 4.0 build 1010 that controls the method to be used.
The key value is DWORD, named "ForceLDAPLevel" and is located in the key: "HKEY_LOCAL_MACHINE\SOFTWARE\teknikhuset\Content Studio\3.2". The value is not needed and but can be created if needed.
There are 3 settings available:
  • Missing or 0 = No action . Content Studio happily continues, authenticates the user and tries the WinNT protocol.
  • 1 = Stop. Will not authenticate the caller if the LDAP binding fails. The caller will see an error message indicating the nature of the error.
  • 2 = Silent. Content Studio logs the error to the Event Log and happily continues authenticating the user and tries the WinNT protocol.
  • 3 = Stop and log. This is a combination of the behavior 1 and 2.
Editing the registry should only be done if you have sufficient knowledge. Improper usage can make your computer or applications behave unexpectedly