Can QMM be configured to use Secure LDAP? (4235502)

Can Migration Manager be used in a locked down environment where standard LDAP is not available but instead, DC communication is relying on LDAPS (secure LDAP)?

In order to switch to Secure LDAP the following attributes need to be changed in project's container in ADAM database.

To do that, please do the following:
IMPORTANT: backup your ADAM database prior to do any changes!
- stop directory synchronization for all domain pairs
- close QMM console
- open ADSIEDIT.MSC and connect to the ADAM database, selecting CN=<name of the project>
- expand CN=AMMProject_<GUID> container, then CN=Projects
- right-click each CN=<GUID> containers underneath, selecting Properties and validate that aelita-amm-Name value is matching the name of the domain pair you wish to modify
- modify the following values:

For the source domain:
aelita-Amm-SrcSSL=TRUE
aelita-Amm-SourcePort=636
aelita-Amm-SourceGCPort=3269

For the target domain:
aelita-Amm-TrgSSL=TRUE
aelita-Amm-TargetPort=636
aelita-Amm-TargetGCPort=3269

After these changes DSA will connect to source and target DCs using SSL ports.

Please note that the following restrictions / limitations apply to such a scenario:

1. If the preferred DC/GC needs to be specified, it has to be set as FQDN.
2. ADPW cannot work with SSL connections, the following ER has been raised - ST58796 ADPW cannot use LDAP over SSL
3. Released add-ins were not tested with SSL mode and should be thoroughly tested prior to use in production.
4. In case of using DSA and ADAM on separate servers following issues may occurs:
   ST57403 Open Project Wizard cannot connect to ADAM over SSL if port number is not 636
   ST58848 [Setup] DSA cannot connect to ADAM over SSL if port number is not 636
   ST58802 SWP cannot connect to ADAM over SSL if port number is not 636

Created from Case 752976.