Encryption Active Directory密码移植/迁移到数据库

我们正在扩展现有的软件产品，该产品使用Active Directory将用户凭据存储到云解决方案以存储用户凭据

我想知道我们如何将这些AD密码迁移/移植到新数据库，而不是要求用户重置密码。我知道我们无法检索普通密码，但我想了解如何移植这些密码并使用特定的解密库来验证这些密码

我们可以将此密码移动到新的SQL数据库，但如何验证密码？我们将使用哪种加密算法和salt？

---

谢谢，

我这个月的大部分时间都在与一位客户合作，他正在将各种Active Directory林整合到一个域中。我们没有使用任何第三方工具—仅使用标准的Microsoft实用程序，即Active Directory迁移工具（ADMT）v3和Exchange迁移向导（Exchange Server 2003部署工具之一）—但它们似乎可以完成这项工作

由于将数百名用户迁移到新帐户（使用新密码）将导致大量支持调用，因此我希望让ADMT密码迁移DLL正常工作。这花了一些时间，但在我的企业支持同事的帮助下（实际上是一个PSS电话），我们找到了一种方法。这是需要的：

（作为参考，源域和目标域均处于Windows Server 2003域和林功能模式，使用service Pack 1和service Pack 2混合运行Windows Server 2003。）

---

可以在ADMT v3迁移指南中找到进一步的建议。

我不是说迁移到另一个LDAP域或其他什么，这是将密码迁移到新的SQL数据库。我们可以将这些密码移动到新的数据库中，但是我们如何验证这些密码呢？我们将使用哪种加密算法和salt？

Make sure that there is a trust in place between the source and target domains.
Install ADMT by running admtsetup.exe and follow the installation wizard on the computer that will be used for the migration (I used a domain controller in the source domain but ideally you would have dedicated computers for migration activities and it seems logical that this should be in the target domain).
If not already created by ADMT, create a new domain local group called domainname$$$. This group must be empty, and is required in order to migrate the sIDHistory information between source and target accounts.
On the domain controller that will be used to export the account information (usually the DC holding the PDC Emulator operations master role for the source domain), create/set a value of 1 for a DWORD registry key called TcpipClientSupport in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\.
In both the source and target domains, ensure that success and failure auditing is enabled for account management.
On a computer with ADMT installed, create a password encryption key for each source domain, by shelling out to a command prompt and entering the following commands:
cd %systemroot%\ADMT
admt key /option:create /sourcedomain:<em>domainname</em> /keyfile:<em>filename</em>.pes
(the domainname can be specified in NetBIOS or DNS format.)
On the domain controller in the source domain that holds the PDC Emulator operations master role, connect to the computer with ADMT installed (e.g. via the c$ administration share) and access the %systemroot%\ADMT\PES folder.
Run pwdmig.exe to install the ADMT Password Migration DLL and follow the installation wizard. During the installation, supply the password encryption (.PES) file that was created earlier.
This is the step that’s not in the instructions – even though the password encyption file was supplied during the installation of the ADMT Password Migration DLL, it still needs to be imported manually on the PDC Emulator, by shelling out to a command prompt and entering the following commands:
cd %systemroot%\ADMT
admt key /option:import /sourcedomain:<em>domainname</em> /keyfile:<em>filename</em>.pes
On the domain controller that will be used to export the account information, create/set a value of 1 for a DWORD registry key called AllowPasswordExport in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\. Note that this key constitutes a security risk and should only be enabled during the period of migration.
Restart the computer with the ADMT Password Migrator DLL installed.
Start the Password Export Server service.

Domain administrator in the source domain.
Local administrator on the computer on which ADMT is installed.
Delegated permissions on OUs that are targets for resource migration in the target domain, including the extended right to Migrate SID History (visible in the Security for an object using the Advanced Features view in Active Directory Users and Computers).