Distributing certificates

By default, the Proxy server creates self-signed certificates during installation to secure the connection between devices and the Proxy server. In order for devices to contact the Proxy server, you must install the client certificate and the server's public certificate on each device that uses the proxy server.

After you install the Proxy server, you can download the certificates from the Device information page. You do not need to purchase certificates to use the Proxy server. If the certificates that are initially generated become compromised, you can generate new certificates using the built-in utility. For more information, see Generating new certificates.

If the address of the Proxy server changes, you must regenerate the certificates so the certificates match the IP address of the device. For information on regenerating the certificates, see Generating new certificates.

There are two certificates that need to be distributed to the devices running the Velocity Client: 

the Proxy server public certificate. The device must have this certificate to verify when it has connected to the correct Proxy server. This provides protection against man-in-the-middle attacks. This certificate is named Neurons Proxy CA by default and has a .cer extension.

The Proxy client certificate. The device uses this certificate to prove it is allowed to access the Proxy server. This certificate contains privileged data, and you should be careful to keep it private and secure. If this certificate is compromised, you may need to regenerate all the certificates for the server and redistribute them in order to keep your network secure. This certificate is named Neurons Proxy Client by default and has a .pfx extension and a password associated with it. You create the password when you download it from the Proxy server.

These certificates can be distributed to the Windows or Android devices manually or through an MDM.

Distributing certificates to Windows devices

On a Windows device, the signing public certificate file should be installed in the Local Machine > Trusted Root Certificate Authorities store. The client certificate should be installed in the Current User > Personal store.

The instructions below are for installing the certificates manually. If you have a tool to manage certificates, download the certificates from the Proxy server UI and then follow the instructions for that tool to ensure the certificates are distributed to the correct places.

Distributing certificates to Android devices

The instructions below are for installing the certificates manually or using Ivanti Neurons for MDM. If you have a different tool to manage certificates, download the certificates from the Proxy server UI and then follow the instructions for that tool to ensure the certificates are distributed to the correct places.

Your MDM tool may use different terminology for the two types of certificates. Generally, what we refer to as the Proxy client certificate is called an identity certificate or client certificate. If the terminology for your MDM tool doesn't match, remember that the Proxy client certificate has a .pfx extension and must have a password associated with it.

On an Android device, after installation the certificates should show up in the Trusted credentials list in the Settings app. To confirm that the certificates are installed correctly, open the Settings app and navigate to Security & privacy > More security & privacy > Encryption & credentials . The Proxy server public certificate should be in the Trusted credentials > User list. The Proxy client certificate should be in the User credentials list.

Distributing certificates to Android devices manually

When you are installing certificates manually, some device manufacturers or OS versions may have the settings for certificates in different places in the UI. These instructions are for a stock Android 15 device.

Distributing certificates to Android devices using Ivanti Neurons for MDM

When you distribute the Proxy server certificates using Ivanti Neurons for MDM, each certificate goes in its own configuration. The Proxy server public certificate is added to a Certificate configuration, and the Proxy client certificate is added to a Identity Certificate configuration.