...

           7. In the appeared window choose Entire Chain, Export Format X.509, tick PEM box and enter the path to the location where AuditProxy is installed. 

               Also, enter the file name for your certificate chain. 

           8. If you use Self-signed certificates, you also have to export Public key. Choose the required certificate from the certificates list and click the right mouse button.

...

                The export procedure is completed.

...

SSL certificate installation for AuditProxy (Elasticsearch Kibana Proxy)

...

              d) Enter the name of the public key file, which you used for export (please see above).

        4 4. If you use Self-signed certificates, you also have to enter the parameter check-cert=false to launch kibana-http-proxy application.

...

           d) In Elasticsearch passphrase field (for HTTPS connection) enter the passphrase, which you use for your keystore.

      3. Save the setting changes and restart AuditDriver.

...

           a) Click on the checkbox next to Enable/Disable HTTPS field.

           b) Enter your keystore type, PKCS12 or JKS, in Server KeyStore Type field.

           c) Enter your keystore file name in Server KeyStore file field.

           d) Enter passphrase for your kesytore in Server KeyStore password field.

           e) Enter passphrase for your private keys in Server PrivateKey password field.

               Image Added

           f) Go to the tab Elasticsearch & Kibana.

           g) Make sure that Enable/Disable HTTPS checkbox is active.

           h) Since all the services are installed on the same server, enter the same values for Keystore type, Keystore file, Keystore password as for the GLOBAL tab.

               Image Added

       5. Click Save button.

       6. Restart AuditServer.

       7. Change the protocol from http to https in the address bar of your browser in order to open AuditServer page through https protocol.

       *** If you use self-signed certificates, there can appear a warning that the certificate, used on the server, is not trusted. In this case, you should add exceptions to each of the URL or import this certificate as trusted to your web-browser (see Web-browser documentation).

                Image Added

      * To investigate potential problems with SSL certificate and the service operation use a log file, which you can find in the folder with this service.

      ** If while launching Audit Server has problems with certificates opening, it can automatically switch to http protocol and let you change the settings.

      *** Attention! If at least one of the ACD modules (AuditServer, AuditProxy, ExportService) runs with http protocol, it does not guarantee the proper operation of ACD in general.

      **** Also, to solve problems with self-signed certificates you may need to add your self-signed certificate to cacert truststore of your Java.

          Please follow the steps as described below:

           a) Launch KeyStore explorer and open cacerts file from /lib/security folder of your Java, used for ACD launch. If you did not change the password, it remains “changeit”.

           b) From Tools menu choose Import Trusted Certificate and choose your certificate chain (see above how to export it).

                   Image Added

           c) Set alias for the imported certificate.

                   Image Added

           d) Save your changes File -> Save.

           e) Restart ACD modules.

Possible problems and ways to find and solve them

Dashboards are not shown in AuditServer

• check if kibana proxy is active in your web-browser (see above)
• check if AuditServer and AuditPoxy are using the same protocol – https
• check if there is https defined in AuditProxy config.json file, kibana section, auditUrl attribute
• check log files in AuditServer and AuditProxy for mistakes
• if you use self-signed certificates, make sure that exceptions for the certificates used for AuditProxy were added to your web-browser (see above)

Reports and indexes Elasticsearch are not shown in AuditServer

• check if elasticsearch proxy is active in your web-browser (see above)
• check if AuditServer and AuditPoxy are using the same protocol – https
• check log files in AuditServer and AuditProxy for mistakes
• if you use self-signed certificates, make sure that exceptions for the certificates used for AuditProxy were added to your web-browser (see above)

AuditDriver cannot sent data to elasticsearch (via AuditProxy)

• turn on logging for the driver and analyze log files
• check that keystore used for AuditDriver works properly and contains the required certificate to access AuditProxy

      * If problems appear, please provide us with full screenshots of ACD modules settings, as well as log files of the services, which have problems.

      ** For rollback https changes:

• Stop ACD components
• copy your backup config files to original place
• start ACD components