Active Directory Services does not request secure authorization over an SSL connection

While you are using a program that uses ADSI to communicate to any Lightweight Directory Access Protocol (LDAP) server that is listening on a port other than the SSL port 636, one of the following symptoms may occur:

• The program cannot bind to the LDAP server by using the ADS_USE_SSL/ADS_USE_ENCRYPTION options in the ADSOpenObject method.
• The program cannot set or change the password even if it binds by using the ADS_SECURE_AUTHENTICATION option.

Also, your program cannot access security descriptors for objects by using ADSI calls if all the trustees are irresolvable from the Security Identifier (SID) to the display name. A trustee is a user, group, SID, or other security principal. Also, the program will not bind by using the Windows security principal to ADAM over the SSL with the ADS_SECURE_AUTHENTICATION option.

If a bind is tried by using both the ADS_SECURE_AUTHENTICATION and ADS_USE_SSL flags, the client will perform only the secure authentication and will not try to perform a simple bind with SSL.

This problem occurs because ADSI is restricted to SSL port number 636 when it makes a bind call to the LDAP server. Also, ADSI does not handle cases where all the trustees are irresolvable. When ADSI calls to bind to ADAM by using a Windows security principal over a SSL connection with the ADS_SECURE_AUTHENTICATION option, ADSI then uses a simple bind call instead of a secure bind call.

Microsoft Windows Server 2003

This problem was corrected in Windows Server 2003.

Microsoft Windows XP

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

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 this specific problem. 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 Web site: 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.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Microsoft Windows 2000

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 this specific problem. 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 Web site: 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.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

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

This hotfix resolves ADSI problems that are related to the SSL, security descriptors, and SSL binding to Active Directory in Application Mode (ADAM).