Configuring the SSL port

The SSL port is enabled and the non-SSL port is disabled while connecting to the Active Directory server.

1. Log on to the Analyzer detail view server or Analyzer probe server through an SSH client (like putty) as a root user.
2. From the Analyzer detail view server or Analyzer probe server, verify the domain name of the Active Directory using the command:

   nslookup domain-name

3. If you cannot resolve the domain name, then add an entry of the following form in the /etc/hosts file:
   Active-Directory-server-IP-address domain-name
4. Import one of the following certificates into the Analyzer detail view server or Analyzer probe server keystore:
   Note: The password for the keystore is changeit.
   • Active Directory Server certificate (CER format).
   • Microsoft Public Key Infrastructure (MSPKI) chain Certificate (CER format), one file that contains all the keys.
5. Upload the CER file at the following location /tmp on the Analyzer detail view server or Analyzer probe server using an FTP client (like WinSCP).
6. Navigate to the Java keystore directory. For example:

   /usr/lib/jvm/java-17-amazon-corretto/lib/security

7. If the jssecacerts file does not exist, create it.
8. Import the certificate into the Analyzer detail view server or Analyzer probe server using the command:

   keytool -importcert -alias Alias_name -keystore Truststore_file_path -storetype jks -storepass Truststore_file_password -file Active_Directory_Server_certificate_or_MSPKI_chain_certificate_file_path

   Note: You can define any unique alias name for the certificate.

   For example:

   keytool -importcert -alias detailviewAD -keystore jssecacerts -storetype jks -storepass changeit -file /tmp/LAB_chain.cer

9. Make sure that the megha user has the read permission for the jssecacerts file. If not, change the permission as follows.

   For example:

   chmod o+r jssecacerts

10. Stop the crond service and verify the status:

    service crond stop

    service crond status

11. Stop the megha service and verify the status:

    /usr/local/megha/bin/megha-jetty.sh stop

    /usr/local/megha/bin/megha-jetty.sh status

12. Start the megha service and verify the status:

    /usr/local/megha/bin/megha-jetty.sh start

    /usr/local/megha/bin/megha-jetty.sh status

13. Start the crond service and verify the status:

    service crond start

    service crond status

    Note: If you upgrade the JDK in the future, make sure that the jssecacerts file is copied to the upgraded JDK directory.

    For example: If you upgrade JDK from v1.8.0 to v17, copy the jssecacerts file from/usr/java/jdk1.8.0_291-amd64/jre/lib/security to /usr/lib/jvm/java-17-amazon-corretto/lib/security.

    After copying the jssecacerts file, make sure that megha user has the read permission for the jssecacerts file. If not, set it as in this example:

    chmod o+r jssecacerts

14. Access the Analyzer detail view or Analyzer probe UI as an administrator user, and then add the Active Directory users.