System Administrator Guide 

Enabling Secure Sockets Layer (SSL) for Quark Publishing Platform Server

You can configure Quark Publishing Platform with different security options. In addition to your own network security specifications, you can specify SSL protocol for your Quark Publishing Platform client applications.

SSL support

You can configure your application server containers and all Quark Publishing Platform clients to run in secure mode with SSL technology. This section explains the configuration process.

It is also possible to run Quark Publishing Platform without embedding Tomcat in JVM. See "Deploying in external Tomcat" for information about setting up Quark Publishing Platform without embedding Tomcat.

To manage Web applications in the Quark Publishing Platform environment, Quark Publishing Platform Server embeds an instance of Apache Tomcat 7.0.77 in its JVM. The four Web applications in Quark Publishing Platform include Quark Publishing Platform Web Client, Quark Publishing Platform Console, Quark Publishing Platform Renderer Manager, and Quark Publishing Platform Web Services.

When you enable SSL, it applies to all Quark Publishing Platform client applications deployed in Quark Publishing Platform Server.

Enabling SSL in Quark Publishing Platform Server

The instructions below address two scenarios. The "server.xml" file you edit contains XML tags for both scenarios, which you need to enable or disable by "commenting" and "uncommenting" specific tags.

To enable SSL for secure HTTP for all Quark Publishing Platform Web applications:

  1. Open the "server.xml" file located in the {install_path}/conf folder.

  2. Comment the following tag:

    <Connector port="61400" maxHttpHeaderSize="8192"maxThreads="150" minSpareThreads="25" maxSpareThreads="75"enableLookups="false" redirectPort="61399" acceptCount="100"connectionTimeout="20000" disableUploadTimeout="true" />
  3. Uncomment the following tag:

    <Connector port="61399" maxHttpHeaderSize="8192"MaxThreads="150" minSpareThreads="25" maxSpareThreads="75"enableLookups="false" disableUploadTimeout="true"acceptCount="100" scheme="https" secure="true"clientAuth="false" sslProtocol="TLSv1.2" />
  4. Replace 61399 with 61400 (or any port on which Tomcat will be listening for secure connections).

  5. Save and close "server.xml."

  6. On Quark Publishing Platform Server machine, open the command prompt and execute the following command:

    %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA

  7. Provide the details in the prompts. Password should be changeit.

  8. Restart the Quark Publishing Platform Server.

  9. Access the Admin webpage: https://servername:61399/admin

    This configuration creates one keystore with a private and public key pair. This is a self-sign certificate.

  10. For more information on SSL configuration, including the use of a Certificate Authority, please see the Apache Tomcat SSL information here: url:https://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html

This change means Quark Publishing Platform client applications can use HTTPS. For example, the URL for a Quark Publishing Platform Web Client user would be as follows: https://[server name]:61399/workspace.

Configuring the Platform server console to run with an SSL enabled server

To run the server console with an HTTPS enabled server: 

  1. Open the "Quark.QPP.ServerConsole.exe" file in the [QPP Server]/console folder.

  2. Set useSSL="true".

  3. In <add key="serverHost" value="localhost"/>,enter the server name contained in the SSL certificate.

  4. Open the "ServerApp.properties" file in the [QPP Server]/conf folder. 

  5. Change the port number in  webServer.port=61400 to that of the SSL port, typically 443.

  6. Restart the console.

Configuring Platform clients to log on to an SSL enabled Server

macOS QuarkXPress and QuarkCopyDesk users must fetch a SSL certificate from Quark Publishing Platform Server before they can log on. To do so, each user should launch Terminal and run the following command, substituting the IP address of the Quark Publishing Platform Server computer for [server name]:

echo | openssl s_client -connect[server name]:443 > [server name].pem

for El-Capitan and Sierra MAC OS the command is:

echo | openssl s_client -connect[server name]:[Port] -servername[server name] > [server name.pem

This command retrieves a copy of the server certificate named "[server name].pem". Put this file in the ~/Library/Application Support/Quark/QPP/Certificates folder (or, if you have customized the plist file at ~/Library/Application Support/Quark/QPP/[QPP Framework Version], put the file there).

If the "Quark Publishing Platform" and "Certificates" folders do not already exist at the above locations, create them there manually.

Quark Publishing Platform clients running on Windows do not require a server-based SSL certificate.

Verifying and using SSL

To verify and use SSL:

  1. Start the Quark Publishing Platform Server.

  2. Test Quark Publishing Platform Web Client access by entering the following:

    https://[machine IP/name]:61399/workspace.