Article ID: 2443871 - Last Review: October 21, 2011 - Revision: 6.0 FIM 2010 Self Service Password Reset now supports Enforcement of all domain password policies
On This PageSUMMARYImportantThe changes that are outlined in this document have to be implemented in a test environment before you deploy the change to a production environment.Server certificates are required on any domain controller that holds, or may hold, the PDC emulator FSMO role. This change should be discussed with the appropriate IT groups to make sure correct testing and rollout of LDAP SSL in the production environment. If a problem occurs in production where Self-Service Password Reset no longer works after you implement this change, disable the new functionality in the Registry to return FIM to the original SSPR functionality. Password ResetPassword reset in the Active Directory is historically been done in proxy by helpdesk personnel or user administrators. In this scenario, it is important to buffer those working in proxy from the end-user’s password history to preserve security.With the release of Microsoft Forefront Identity Manager (FIM) 2010, Microsoft offers an application that enables end-users to reset their passwords without calling helpdesk. In this scenario, it is important to enforce all password policies so that users do not use the Self-Service Password Reset functionality in FIM to bypass organizational policies. Until this change, all Windows APIs available to reset passwords in the domain did not enforce all domain password policies. This document describes how to install and configure Self-Service Password Reset in FIM 2010 to enforce all password policies configured in the domain. Password Operations in the Active Directory Management Agent in FIM 2010Since MIIS 2003, the Active Directory management agent uses the Kerberos APIs for both Change Password and Reset Password operations. With the change described in this document, a new way of resetting passwords is added to the Active Directory management agent. You can use LDAP APIs over an LDAP SSL connection.Overview Steps to enable Password Policy Enforcement in FIM SSPR
MORE INFORMATIONFile and Installation InformationComponents for both Windows Active Directory and Forefront Identity Manager must be installed to enable this new functionality.Collapse this table
Installation InstructionsfDomain Controller OverviewRequirements
Installing the hotfix update for WindowsUse the Run as Administrator option when you run the appropriate executable documented in the following table on the domain controller.Collapse this table
To make sure that the hotfix is installed as expected, LDP.exe can be used to check for the new LDAP control that is installed with the hotfix. LDAP control information is returned in the “supportedControl” attribute in the RootDSE. New Control OID: "1.2.840.113556.1.4.2066" Please see Appendix 4 for more information about checking the RootDSE for this new control that uses ldp.exe.FIM 2010 Server ComponentsDownload and then install the following FIM 2010 server components:
Configuration StepsLDAP over SSL ConnectionsThe basic requirements for establishing an LDAP connection over SSL to a domain controller:
Enabling Password Policy Enforcement in FIM 2010Enabling password history enforcement in FIM 2010 is finished by making a registry setting. This must be configured for each Active Directory management agent on which we want to enable password policy enforcement.Important By default, this setting is disabled for all Active Directory management agents. Note In the following Registry Key example, <ma name> should be replaced with the name of the Active Directory MA to be configured. Registry Key: SYSTEM\CurrentControlSet\Services\FIMSynchronizationService\Parameters\PerMAInstance\<ma name> Registry Value:Set ADMAEnforcePasswordPolicy = 1 to enforce password history. All other values are interpreted as turning off the new functionality. Testing and TroubleshootingThe appendixes at the end of this document provide additional information that may be helpful when you configure a simple test environment. There are also links for troubleshooting LDAP over SSL connections.Appendix 1: Set Up A Simple Test ConfigurationNote The steps in this appendix are not meant to be used in a Production environment. The planning and deployment of certificates in the production environment should be carefully considered for the whole security infrastructure of the network. Enable LDAP SSL in a Test Environment that uses Active Directory Certificate Services to issue the server cert to the domain controller. Install Active Directory Certificate Services
Configuring the Domain Controller Certificate Template to enable Enrollment
Requesting a Certificate for the Domain ControllerOn the Domain Controller
Click the check-box next to “Domain Controller” and then click the “Enroll” buttonTrusting the Root CA on the FIM Sync computerOn the Certification Authority computer
On the FIM Synchronization Service computer
Checking the LDAP over SSL connection to the PDCInstall the Remote Domain Admin Tools
Using Ldp.exe to test the LDAP over SSL connection
If you notice that the connection does not occur, please use the following KB article to troubleshoot: 938703 (http://support.microsoft.com/kb/938703/ ) How to troubleshoot LDAP over SSL connection problems Test the LDAP SSL Connection by using Ldp.exeResulting Text in the LDP results window:Collapse this image ![]() Notice how the server name in the ldap_sslinit() method matches the dnsHostName that is returned in the rootDSE information. The following certificate screen shot shows the name that the certificate is issued to matches this name as well. It is very important for all of these to match. Otherwise the LDAP connection fails and “schannel” logs an error in the event log. Output from the right side pane of LDP.exe after you make the connectionDC Certificate for ComparisonCollapse this image ![]() Notice that the server certificate is also issued to the same dnsHostName. Having all of these match is very important to make an LDAP SSL connection. Appendix 2: Frequently Asked QuestionsQuestion Will this work if I install a Windows Server 2008 R2 domain controller as the PDC Emulator in a Windows Server 2003 or Windows Server 2008 domain? Answer Yes. This functionality is enabled by an LDAP control that is hosted on the PDC emulator. As long as that control is found on the PDC emulator, this will work as expected.Question If I install this update on an existing FIM deployment, will it break the current Self-Service Password Reset configuration? Answer No. By default, this new functionality is disabled in the Active Directory management agent. The following registry information is used to enable the new functionality. Registry Key SYSTEM\CurrentControlSet\Services\FIMSynchronizationService\Parameters\PerMAInstance\<ma name> Collapse this table
Question What is the change to the WMI MIIS_CSObject.SetPassword method to enable this functionality? Answer string SetPassword( [in] string NewPassword, [in] bool ForceChangeAtLogon, [in] bool UnlockAccount [in] bool ValidatePasswordPolicy ); ParametersCollapse this image ![]() Appendix 3: Additional ResourcesCurrent documentation for LDAP over SSL configuration & TroubleshootingFor more information about how to enable LDAP over SSL with a third-party certification authority, click the following article number to view the article in the Microsoft Knowledge Base:321051 (http://support.microsoft.com/kb/321051/ ) How to enable LDAP over SSL with a third-party certification authority For more information about how to troubleshoot LDAP over SSL connection problems, click the following article number to view the article in the Microsoft Knowledge Base: 938703 (http://support.microsoft.com/kb/938703/ ) How to troubleshoot LDAP over SSL connection problems For more information about Windows LDAP over SSL Requirements, visit the following Microsoft website: Example Code for Establishing a Session over SSL
(http://msdn.microsoft.com/en-us/library/aa366105(VS.85).aspx)
Appendix 4: Using LDP.exe to check for the new LDAP Control
REFERENCESFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Other Resources Other Support Sites
CommunityArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top


