Configuring Cloudpaging SSL Certificates
Prerequisites
Customers must request and provide valid SSL Certificates.
Applying the SSL certificate
Windows
Connect to one Cloudpaging Admin Server
Rename the <certificate>.pfx file to cloudpaging.pfx
Copy Cloudpaging.pfx to the first Cloudpaging server and place it in
C:\Program Files (x86)\Numecent\Application Jukebox Server
Backup
C:\Program Files (x86)\Numecent\Application Jukebox Server\core\conf\server.xml
(copy and rename the file)Open Notepad with Administrative privileges and open the original server.xml
Edit the keystoreFile="..." tag (see below), replacing the custom.keystore filename with cloudpaging.pfx
Immediately after that entry add
keystorePass="ThePassword" keystoreType="PKCS12"
(with the correct password)Save server.xml
Restart the Cloudpaging service
Ensure the certificate is applied and Cloudpaging is functional via
https://<server_fqdn>/jukeboxserver
Copy
C:\Program Files (x86)\Numecent\Application Jukebox Server\core\conf\server.xml
to the next Cloudpaging serverRestart the Cloudpaging service
Ensure the certificate is applied and Cloudpaging is functional via
https://<server_fqdn>/jukeboxserver
Repeat steps 10-12 for the remaining Cloudpaging servers
Example Windows server.xml
<Connector acceptCount="100" clientAuth="false" disableUploadTimeout="true" enableLookups="false" keystoreFile="C:\Program Files (x86)\Numecent\Application Jukebox Server\cloudpaging.pfx" keystorePass="password" keystoreType="PKCS12" maxHttpHeaderSize="32768" maxThreads="300" minSpareThreads="25" URIEncoding="UTF-8" port="443" SSLProtocol="TLSv1.2" SSLEnabled="true" scheme="https" secure="true"/>
Linux
SSH into the server through WinSCP with credentials from 1password
Rename the new <certificate>.pfx file to cloudpaging.pfx
Copy Cloudpaging.pfx to the first Cloudpaging server and place it in
/usr/local/ApplicationJukebox/core/
Backup
/usr/local/ApplicationJukebox/core/conf/server.xml
Open Notepad with Administrative privileges and open the original server.xml
Edit the keystoreFile="..." tag (see below), replacing the custom.keystore filename with cloudpaging.pfx
Immediately after that entry add
keystorePass="ThePassword" keystoreType="PKCS12"
(with the correct password)Save server.xml
Restart the Cloudpaging service
Ensure the certificate is applied and Cloudpaging is functional via
https://<server_fqdn>/jukeboxserver
Copy
/usr/local/ApplicationJukebox/core/conf/server.xml
to the next Cloudpaging serverRestart the Cloudpaging service
Ensure the certificate is applied and Cloudpaging is functional via
https://<server_fqdn>/jukeboxserver
Repeat steps 10-12 for the remaining Cloudpaging servers
Example Linux Server.xml
<Connector acceptCount="100" clientAuth="false" disableUploadTimeout="true" enableLookups="false" keystoreFile="/usr/local/ApplicationJukebox/core/cloudpaging.pfx" keystorePass="password" keystoreType="PKCS12" maxHttpHeaderSize="32768" maxThreads="300" minSpareThreads="25" URIEncoding="UTF-8" port="443" SSLProtocol="TLSv1.2" SSLEnabled="true" scheme="https" secure="true"/>
Rollback procedure
Windows
Revert
C:\Program Files (x86)\Numecent\Application Jukebox Server\core\conf\server.xml
Restart Cloudpaging server
Linux
Revert
/usr/local/ApplicationJukebox/core/conf/server.xml
Restart Cloudpaging server
Updating the certificate
If Cloudpaging is not using a Cloudpaging.pfx file, then it should be updated to use one.
Providing the customer uses health check load balancing there will be no outage.
Otherwise, the service will be offline whilst the master (live) server is updated (approx. 5 minutes).
To prevent an outage in the absence of health check load balancing, the secondary server should be updated first and verified. Once complete it should be switched in the load balancer to become the master (live) server. If manual switch over is required, it should be scheduled so the load balancer can be updated.
If there is only one server, the service will be:
At risk from the start of the change for approx. 15 minutes
Offline for approx. 5 minutes whilst the service restarts
Update Procedure
Copy cloudpaging.pfx to cloudpaging.bak
Overwrite cloudpaging.pfx
Restart the service
Check the Portal loads (https://localhost/jukeboxserver)
Repeat steps 2-4 on the other servers
Rollback Procedure
Copy cloudpaging.bak to cloudpaging.pfx
Restart the service
Check the Portal loads (https://localhost/jukeboxserver)