Open a command prompt window and change to the directory [app-path]/runtime/jre/bin. Any existing files called 'my-ssl-keystore' in this directory are likely leftovers from previous attempts and need to be renamed or deleted at this point.

Enter this command to produce the SSL key:

keytool -keystore [app-path]\server\custom\my-ssl-keystore -alias jetty -genkeypair
    -keyalg RSA

As keystore password choose 'password' or another simple password as it is not very important. Enter the same password again later when asked for a key password.

Note: Some organizations require larger key sizes than the default 1024 bit. In this case add the "-keysize 2048" or "-keysize 4096" parameter to the end of the above command line.

You will be asked a series of questions. Enter the exact fully-qualified domain name of the PaperCut MF Application Server where it asks you for "first and last name". The server name must be the exact one that users will enter into their browsers to access PaperCut MF's web interface, e.g. 'printing.myschool.edu'. Depending on the certification authority's requirements you may also need to fill in some of the other fields.

Enter keystore password:  password
What is your first and last name?
  [Unknown]:  printing.myschool.edu
What is the name of your organizational unit?
  [Unknown]:  
What is the name of your organization?
  [Unknown]:  
What is the name of your City or Locality?
  [Unknown]:
What is the name of your State or Province?
  [Unknown]:
What is the two-letter country code for this unit?
  [Unknown]:
Is CN=printing.myschool.edu, OU=Unknown, O=Unknown,
L=Unknown, ST=Unknown, C=Unknown correct?
  [no]:  yes

Enter key password for <jetty>
        (RETURN if same as keystore password):  password

Prepare your new SSL key for certification by the certificate autority:

keytool -certreq -alias jetty -keystore [app-path]\server\custom\my-ssl-keystore
    -file [app-path]\server\custom\jetty.csr

The contents of the resulting jetty.csr can be pasted into the online order forms of abovementioned commercial certificate authorities or passed to your organization's own certificate authority.

When the certification process has completed, the authority will provide you with a certificate file that can be downloaded from the autority's web site. The filename will usually end in .crt, .cer or .cert. The contents of the file should look something like this:

-----BEGIN CERTIFICATE-----
MIIDLTCCApagAwIBAgIQJc/MOTjAW0HrPI/4rGtDCDANBgkqhkiG9w0BAQUFADCB
hzELMAkGA1UEBhMCWkExIjAgBgNVBAgTGUZPUiBURVNUSU5HIFBVUlBPU0VTIE9O
 ... more here ... 
Awjhfz9EfxN2l1UYP15xZZyNO4DO3X/LliCG9pdFf4hUHl8tRnhQBvRR1F0v9UHB
PC6L9jNjMbQUoQ9NG/S8Nn7ZcSHNy+P53ntIBaEfTv7+qvXNWvSb5wj4pd05wGF1
Bw==
-----END CERTIFICATE-----

Save the file as jetty.crt.

Before you can make use of your newly obtained certificate, you may have to import the certificate authorities "root certificate". PaperCut comes with a number of root certificates pre-installed that you can list using this command (still from the directory [app-path]/runtime/jre/bin as above):

keytool -keystore ../lib/security/cacerts -storepass changeit -list

Add the option "-v" at the end to obtain the same list with more details, such as expiration dates.

If your certificate authority is not listed there, or you have been notified that they have recently started using new root certificates, then you need to first import the certificate authority's root certificate into your keystore before importing your newly obtained own certificate. The CA's root certificate will usually be available for download on the CA's web site as a file ending on .pem or .crt. Save the file using a filename indicative of the CA's name, e.g. globaltrust.pem. Import the root certificate using this command, specifying an alias that is indicative of the CA's name (type this all in one line):

keytool -keystore [app-path]\server\custom\my-ssl-keystore -importcert -alias globaltrustroot 
    -file globaltrustroot.pem

When asked whether to trust this certificate, answer yes:

Trust this certificate? [no]:  yes

Some certificate authorities also provide additional "intermediate certificates" that will have to be imported the same way as the root certificate. You should use a different alias each time. For example:

keytool -keystore [app-path]\server\custom\my-ssl-keystore -importcert -alias globaltrustinter 
    -file globaltrustinter.pem

Now you can import your own certificate previously saved as jetty.crt (type this all in one line):

keytool -keystore [app-path]\server\custom\my-ssl-keystore -import -alias jetty
    -file jetty.crt -trustcacerts

Your new keystore file my-ssl-keystore is now ready and should be moved to the location [app-path]/server/custom.

Open the Windows Control Panel and open Internet Options.

On the "Content" tab click "Certificates".

On the Personal tab select the certificate and click "Export ..." and click "Next" at the initial screen

Select 'Yes, export the private key' and click Next

If you selected the last option correctly, you will only be able to export as a .PFX file

Type in a password for the PFX file. This is only used temporarily.

Save the PFX file to with the extension .pfx. (This is just temporary, you MUST delete this file later on.)

Finish the wizard to export the certificate.

Open the Windows management console, select your IIS server and open "Server Certificates".

Right-click the certificate and click "Export ...".

Choose a filename with the extension .pfx. (This is just temporary, you MUST delete this file later on.)

Type in a password for the PFX file. This is only used temporarily.

Click OK.

Open a command prompt and change to the installation directory. E.g. on Windows:

    cd "c:\Program Files\PaperCut MF\"

Enter the following command (type this all in one line):

"runtime/jre/bin/java" -classpath server/lib/jetty-6.1.22.jar
    org.mortbay.jetty.security.PKCS12Import "<pfx file>"
    server/custom/my-ssl-keystore

Substitute <pfx file> with the .pfx or .p12 file containing your certificate and key.

The Jetty version number (6.1.22) changes from time to time. If you receive a NoClassDefFoundError message look for a jetty-*.jar file in the [app-path]/server/lib/ directory and update the command as appropriate.

You will be asked to enter the 'input keystore passphrase'. Enter the password that you used when you saved the file.

You will be asked to enter the 'output keystore passphrase'. Enter a new password such as 'password'. Once this command completes a new file should be created at [app-path]/server/custom/my-ssl-keystore. This file is your keystore and contains your certificate and key.

Now that you have your keystore file, follow the instructions in the section called “Configuring PaperCut to use the new certificate” to install it and start serving up your new SSL certificate.

Copy your signed keystore onto the server running the PaperCut MF Application Server. The suggested location is [app-path]/server/custom/my-ssl-keystore

Open the file [app-path]/server/server.properties with a text editor (e.g. Notepad).

Locate the section titled SSL Key/Certificate.

Remove the # (hash) comment marker from all lines starting with "server.ssl".

Define the location of your keystore, keystore password and key password as chosen previously. The file should look something like this:

    server.ssl.keystore=custom/my-ssl-keystore
    server.ssl.keystore-password=password
    server.ssl.key-password=password

NOTE: On Mac OS please specify the FULL path to your keystore, e.g. /Applications/PaperCut MF/server/custom/my-ssl-keystore

Restart the PaperCut MF Application Server and verify all is working. If the server fails to start, error messages will be recorded in logs located in the server's logs directory.