5.12.0 5.11.0 5.10.0 5.9.0 5.8.0 5.7.0 5.6.0 5.5.0 5.4.0 5.3.0 5.2.0 5.1.0 5.0 4.10 4.9 4.8 4.7 4.6 4.5.3 4.5.2 4.5.1 4.5 4.4 4.3
5.12.0 5.11.0 5.10.0 5.9.0 5.8.0 5.7.0 5.6.0 5.5.0 5.4.0 5.3.0 5.2.0 5.1.0 5.0 4.10 4.9 4.8 4.7 4.6 4.5.3 4.5.2 4.5.1 4.5 4.4 4.3
Breadcrumbs

MYSQL SSL Connection Configuration for Reporting


The MYSQL Server must be configured to accept the SSL Connection.


  1. Get the MySQL key-store (.jsk) & certificate(.cert) files from customer. The .jsk file is required for configuration of the reporting connector, whereas the .cert file is required for Apache Superset SSL configuration.

    Skeleton Project (cim-solution) already contains the default .jks files in the keystore directory.


  2. Replace the mykeystore.jks file acquired from the customer in cim-solution/kubernetes/pre-deployment/reportingConnector/keystore/ directory.

  3. Navigate to cim-solution/kubernetes/ directory and run the following command.

    JavaScript
    kubectl create configmap -n expertflow ef-reporting-connector-keystore-cm --from-file=pre-deployment/reportingConnector/keystore/mykeystore.jks


  4. Open the cim-solution/kubernetes/pre-deployment/reportingConnector/reporting-connector.conf and set the mysql_dbms_additional_params value as shown below.

    mysql_dbms_additional_params=noDatetimeStringSync=true&useSSL=true&requireSSL=true&trustServerCertificate=true&clientCertificateKeyStoreUrl=file:///root/config/certs/mykeystore.jks&clientCertificateKeyStorePassword={KEYSTORE_PASSWORD}

# Replace the {KEYSTORE_PASSWORD} with your original keystore password. Use "changeit" in case of default password.