2021.1

Table Of Contents
Note
The Root certificate, Certificate and Key files must be in the PEM format (ASCII
base64 encoded). Files in DER format, the binary encoded version of the PEM
format, cannot be used to configure Workflow, although they may have the same file
extension (e.g. .crt, .cer). Please check the format of your files, using a tool like:
https://www.httpcs.com/en/ssl-converter.
l
Root certificate: Enter the absolute path to the public key certificate identifying the
root certificate authority. The file generally has a .crt extension and is obtained from
a Certificate Provider such as Thawte or Verisign. If the Root Certificate and
Certificate file are identical, this is considered a self-signed certificate, which is
considered unsecured by most browsers.
l
Certificate: Enter the absolute path to the public key certificate identifying the
certified server. The file generally has a .crt extension and is provided by a
certificate provider, or through the use of certificate generators such as openssl or
makecert.com.
l
Key: Enter the absolute path to the Private Key file. This file generally has a .key
extension.
l
Password (optional): Enter the password (or passkey) for the Private Key file. The
maximum length of this password is 64 characters.
This password is encrypted within PlanetPress Workflow server and is not saved in
plain text.
l
Encryption protocol: Choose your cryptographic protocol (SSL or TSL). This is
determined by the software that generated the keys. The service uses SSL 2.3 or
TLS 1.0.
Note
When SSL is enabled and a user sends a query prefixed with https://, then this
specific communication will be sent through port 443, which cannot be changed in
Workflow. However, http:// requests will still be received on the port specified in
http server preferences.
Page 790