This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
on 02-22-201908:29 AM - edited on 02-27-202001:10 PM by KylieF
How To: Enable SSL using the Connect 2019.1 Installer
With version 2019.1, you can make Connect run on https protocol and make the communication between client and server much more secure. This is an enhancement from the previous version, when you had to manually change configuration files, download SSL tools and execute several of commands. Now you can do it in a user friendly way just by using the Installer.
Note: SSL is a very broad topic and not every situation can be handled by the Installer (as opposed to CLI - command line interface).
In the 2019.1 version, we've focused on the more simple scenario - generating the self-signed certificate with the request file you can use to get the signed certificate (not mandatory).
The second (and more common) scenario, when you already have a certificate with the private key, cannot be directly achieved with the 2019.1, and the import must be done using CLI.
We plan to continue with enhancing the SSL configuration capabilities in the next releases.
Alteryx Connect 2019.1
Private key - the part of certificate that is private only for you, is created with the creation of a keystore and is stored in it.
Public key - the part of certificate you share with the world in order to establish trust.
Intermediate Certificate -
Certificate Signing Request (CSR)
Certification Authority (CA)
CA signed certificate
Part one - running with self-signed only
Run the AlteryxConnect_2019.1.exe file.
If you don't have Connect installed, you have to install Connect first. Continue the install process until you see the "Enable SSL" option and continue from step #6 of this tutorial.
Otherwise, you will see a screen with several options:
Upgrade (depending on the installed version)
Remove existing installation
The upgrade includes the option to enable SSL as well. For the purpose of this guide, and because I already have 2019.1 installed, I'm selecting Enable SSL. I recommend that you upgrade as well but it is not mandatory. You can use this Installer to set up SSL even for the previous versions (not version 1).
If Connect is running, you will have to stop the service. Click the Stop service button and wait until another screen appears (it should take few seconds).
You want to Set up SSL, so leave that checkbox selected (or select if unchecked) and choose between the two offered options. This screen also displays during the Install and Upgrade scenario.
Upload existing certificate - this scenario allows you to select an existing keystore or create a new one, create a CSR file and upload the signed and intermediate certificates.
Generate self-signed certificate - choose this scenario if you want to use only a self-signed certificate and don't plan to get the signed one (e.g. just for testing purposes).
Select the Upload option, since the additional screens can be skipped.
Upload existing certificate
On this screen you can change the port for https and have to select existing keystore or create a new one. You can only browse for the folder and the filename must be written separately. Let's assume you don't have any keystore so far:
Specify the password for the keystore - since it contains your Private key, you have to have it password protected otherwise you cannot continue. Don't forget the password as it will be needed later.
You can leave the default values for filename and path or choose your own.
Uncheck the 'Redirect http communication' only if you want your users to type "https://" in the URL, but usually you should keep that option checked.
Click Next (inactive if password not specified).
If the selected port is already used, you are notified and have to either release that port or go Back to select a different one.
Port 443 in use
Here we are going to specify our self-signed certificate. If you already have a keystore with certificate, skip this step.
Alias - is the identifier of the certificate in your keystore. You can type in whatever you want, but only use lowercase letters.
Domain - should match your URL you're going to use to access Connect.
All other options are self-explanatory - do not use special characters.
This information will be presented to the user if he/she chooses to see your certificate in the browser, so choose them wisely.
I recommend creating the CSR file - you don't have to use it, but if you decide to get your certification signed, it is easier to take already existing CSR file than to create it. This step can be skipped, e.g. if you are using already existing keystore with a certificate.
Just specify the filename
The path says where will the CSR file be created. You can leave the default value which is Connect folder.
Now I am on the Import certificate page. As I mentioned in the beginning of this post, in the 2019.1 only the certificate signed based on the CSR file created in the previous step will lead to a successful startup of Connect. So at this point you have these options:
Click Next and don't import anything - this will lead to a (most likely) successful start of Tomcat on https with the self-signed certificate and once you get the certificate signed you can go back on this page (skip the previous ones) and import it here.
Provide your IT department with the CSR file and wait until they give you a signed certificate back. In such case don't forget to click the Import button once you specify the alias, path and filename of the certificate. You also have to first import the certificate of the CA (the body that signed your certificate) otherwise the keystore doesn't trust the signature and won't let you import it.
For demonstration purposes, I'm not importing anything now and go to the next screen.
Start the service - leave the checkbox selected and press Next. Notice I'm running https on port 4430.
While the service is starting, you can check catalina.log in logs folder. If you find this row (depending on your https port) there:
then your SSL setting and keystore are properly configured.
Once the service is up and running, click Next.
Click Finish to open Connect in your browser.
You will probably see a page similar to this:
You can also check the SSL certificate on the top of the page - it should show the same values you used to create the certificate in step #10.
Depending on your browser, you should be able to accept the risk and proceed to the page.
Finally, you will get to the Connect page.
You get the warning from your browser because it does not trust the SSL certificate the application is using, which is expected behaviour. It is not verified by any trusted party. So in order to have it trusted, you have to either import the certificate to every machine you want to access Connect from (could be manageable by GPO), but that is not a best practice, or you can get verification from a certification authority (CA) - a body that your browser trust. By getting that certificate signed by it, you establish a chain of trust. For that, you need to provide them with the CSR file you've created in step #11.
Once you get the file back, continue with part two.
Part Two - Import the Signed Certificate
Once you receive your certificate signed, run the Installer again.
Get to the Import screen, i.e.
Enable SSL -> Stop the service -> Upload existing certificate -> keep the keystore settings as is -> Skip creating self-signed certificate -> Skip creating CSR file
You are on the Import screen. First you have to import the certificate of the CA. Usually they have them on their website ready for download. The certificate must be in X.509 format, i.e. it should have extension either crt, pem or der.
Alias - use any value, e.g. 'ca''
Certificate file - filename of the CA certificate.
Path to file - select the folder the CA certificate is in.
Click Import. You should see a green status that the certificate was imported successfully.
Stay on the Import page and import your signed certificate. The certificate must be in X.509 format, i.e. it should have extension either crt, pem or der.
Alias - use the same as previously, in my case 'mycert'
Certificate file - filename of the signed certificate
Path to file - select the folder the signed certificate is in
Click Import. You should get a green status again.
Click Next, Start the Service and Open Connect in browser.
The icon next the URL should be green now and your browser should not warn you about unsecured website.
Cannot create Keystore
This could be because the keystore alias has already been used.
Or because there are forbidden characters in the fields, e.g. 'Alteryx, Inc.' is an invalid value.