Java 1.8.0_121 and above causes QSJ licenses to fail. - "Error verifying license: Invalid encoding for signature" (4263091)

After upgrading Java to 1.8.0_121 or higher the license will no longer work if the license file was generated prior to 2015.

"Error verifying license: Invalid encoding for signature" might be seen in the logs.

RESOLUTION #1

You can contact licensing and request to have a new license file generated that can be used within the product to resolve this issue.

RESOLUTION #2

You can update the certificate in your existing license with the certificate that is attached to this article.

Prerequisites:

• Download the attached certificate that is named qsj-certificate-update.zip and unpack it on a local system.
• In a shell either on Unix or Windows make sure you are in the directory with the certificate.
• Copy your existing license file (vsj-license.jar or jcsi_license.jar) into that same directory.
• You can run the 'jar' command from your Java installation.  Any Java installation that includes the 'jar' command will suffice;  the version does not matter.  (A JDK installation does include the 'jar' command whereas the JRE generally does not).  A convenient way to do this is to include the $JAVA_HOME/bin on your PATH in a Unix or Linux environment.

The steps below refer to "vsj-license.jar", but if your license JAR is named "jcsi_license.jar", use that instead.  (The filename is unimportant;  only the contents matter).

Step 1:  Run "jar tfv vsj-license.jar".  This will list the resources in the existing license JAR file.  Check the entry for the existing "jcsi.licensing.cert.pem" resource:

• If its length (the first column of output from the 'jar tfv' command) is already 774 bytes then the JAR file already contains the new certificate and no further action is needed.
• If its length is 700 bytes then it is the old certificate and must be updated, per the steps below.

Step 2:  Run "jar uf vsj-license.jar jcsi.licensing.cert.pem".  This updates the JAR file to include the new certificate.

Step 3:  Run "jar tfv vsj-license.jar" again to check the results.  The size shown for the "jcsi.licensing.cert.pem" resource should now be 774 bytes.  There must be only one "jcsi.licensing.cert.pem" resource, not two or more.

Step 4:  Replace the existing vsj-license.jar in your VSJ-enabled applications with the updated vsj-license.jar