An LDAP simple bind to a Windows Server 2008 R2-based domain controller fails when the user name has more than 255 characters in the distinguished name

S’applique à : Windows Server 2008 R2

Symptoms


Consider the following scenario in an Active Directory domain environment:
  • You log on to a client computer by using a user name that has more than 255 characters in the distinguished name (DN).
  • You perform a Lightweight Directory Access Protocol (LDAP) simple bind operation from the client computer to a Windows Server 2008 R2-based domain controller.
In this scenario, the LDAP simple bind authentication fails. Additionally, you receive an error message that resembles the following:
Copy Code Error <49>: ldap_simple_bind_s() failed: Invalid Credentials
Server error: 80090308: LdapErr: DSID-0C0903AA, comment: AcceptSecurityContext error, data 57, v1771
Error 0x80090308 The token supplied to the function is invalid

Cause


This issue occurs because Windows Server 2008 R2 limits the distinguished name of a user to 255 characters in LDAP simple bind operations.

Resolution


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites to apply this hotfix.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very important for maintaining the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Pwdssp.dll6.1.7600.2080515,87225-Sep-201005:23x64

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information


For more information about the Lightweight Directory Access Protocol, visit the following Microsoft website:For more information about the ldap_simple_bind function, visit the following Microsoft website:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_59f2cbcc70959f150b9cc6c8e79f8d2d_31bf3856ad364e35_6.1.7600.20805_none_d5cf4735f3e792c6.manifest
File versionNot applicable
File size707
Date (UTC)27-Sep-2010
Time (UTC)18:47
PlatformNot applicable

File nameAmd64_microsoft-windows-security-pwdssp_31bf3856ad364e35_6.1.7600.20805_none_700f2978280914b3.manifest
File versionNot applicable
File size2,524
Date (UTC)25-Sep-2010
Time (UTC)05:54
PlatformNot applicable

File nameUpdate.mum
File versionNot applicable
File size1,706
Date (UTC)27-Sep-2010
Time (UTC)18:47
PlatformNot applicable