The ACL Connector for Analytics Exchange supports Secure Sockets Layer (SSL) encryption on the connections between client machines and AX Server. If SSL is enabled, the connector uses OpenSSL to encrypt all data moving across the network connections between client machines and the server.
To configure SSL using certificates, you must generate a set of SSL certificates on the server machine. You can generate one of the following certificate types for the SSL connection:
Download and install OpenSSL and then add the path to the openssl.exe executable to your PATH environment variable.
Note
Like many open source software projects, the OpenSSL project does not distribute any code in binary form. Instead you must download the project source code and build the binary or locate a binary that is distributed for your operating system from a third-party source.
For more information, see the OpenSSL documentation.
Use OpenSSL to generate a key file and certificate file on the server machine. Self-signed certificates are useful during development or testing, when you do not need to purchase a commercial certificate.
md C:\newcerts
cd C:\newcerts openssl req -x509 -newkey rsa:4096 -keyout server-key.pem -out server-cert.pem -days 365 -nodes
You are prompted for information which is incorporated into the certificate, such as Country, City, Company Name, and so on. Make a note of the information you enter as you may get prompted for this information again at a later stage.
Note
The -nodes argument removes password-protection for the private key so you do not need to enter a password when you restart the server.
Result the self-signed certificate is created. You require server-key.pem and server-cert.pem during the installation of the ACL Connector for Analytics Exchange on the AX Server machine. Client users do not require a certificate file when using this option.
Like self-signed certificates, Certificate Authority (CA) certificates ensure no third-party can easily access the connection. However, CA certificates provide additional trust because an independent, trustworthy certificate authority validates the server's authenticity.
md C:\newcerts
cd C:\newcerts openssl genrsa -out server-key-withPass.pem
openssl req -new -key server-key-withPass.pem -out signingReq.csr
You are prompted for information which is incorporated into the certificate, such as Country, City, Company Name, and so on. Make a note of the information you enter as you may get prompted for this information again at a later stage. When asked for an email address, provide a valid email address so that the Certificate Authority can send the certificate via this address.
Result if the request is successful, the Certificate Authority sends you a certificate using the email address you provided in the signing request. The email you receive includes an encrypted CA certificate and a link to an encrypted CA intermediate certificate.
Copy both certificates to a text file, with the non-intermediate certificate followed by the intermediate certificate and then save the file as CA-cert.pem. You require this file for the following section.
cd C:\newcerts
openssl CA -in signingReq.csr -out server-cert.pem -keyfile server-key-withPass.pem -days 365 -cert CA-cert.pem
openssl rsa -in server-key-withPass.pem -out server-key.pem
Caution
Once you remove the requirement for the password, the certificate can be copied and used elsewhere. Therefore, once you remove the password requirement, you must take adequate precautions when storing the file. Ensure that the permissions are set to only allow access to those who need it.
Result the server certificate is created and signed.
Once you generate a self-signed or CA certificate, you have a full set of SSL certificates that you can distribute: