External to Directory Sync Pro for Active Directory, the following server configurations are necessary to set up the environment for FIPS Mode.
Windows Server 2012 R2 or later must be installed and up to date.
The following group policies must be enabled:
System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.
Ensure this policy is enabled.
Network Security: Configure encryption types allowed for Kerberos.
Ensure the “AES128_HMAC_SHA1” and “AES256_HMAC_SHA1” values are selected.
NOTE: Authentication of target accounts with synchronized passwords requires Kerberos encryption type “RC4_HMAC_MD5” to be allowed for participating devices.
Insecure SCHANNEL Server protocols must be disabled.
SSL 2.0, SSL 3.0, TLS 1.0, TLS 1.1
SSL certificate for Web Hosting issued by a trusted certificate authority.
For environments with existing Directory Sync Pro for Active Directory installations, the installation must be upgraded to version 20.11 or later. If the existing installation is configured with fail-over nodes, each node must also be upgraded to version 20.11 or later.
For new installations, Directory Sync Pro for Active Directory 20.11 enforces all FIPS mode requirements, no additional steps are required.
Ensure the certificate and CA certificate chain has been installed on the server.
Open Internet Information Services (IIS) Manager.
Expand the Sites node in the Connections pane.
Right-click the “DirSync” website node and choose “Edit Bindings…”.
If the site has an “https” binding, select it and click “Edit…”
If the site does not have an “https” binding, click “Add…”
From the “Type” drop-down, select “https”.
From the “SSL certificate” drop-down, select the appropriate certificate.
Remove the “http” binding.
In the IIS Manager Features View pane, double-click “SSL Settings”.
Check the “Require SSL” checkbox and click “Apply” in the Actions pane.
Validate the website can be accessed and the bowers is indicating the certificate is valid and trusted.