Reset Search



KB40579 - Java Secure Application Manager (JSAM) fails to launch after upgrading to Java 8 update 131

« Go Back


Last Modified Date4/24/2017 3:09 PM
This article describes an issue where JSAM fails to launch after upgrading the Oracle Java JRE client to Java 8 update 131 (or higher) if running PCS 8.1R11 (or lower version)
Problem or Goal
After upgrading to Java 8 update 131, Java Secure Application Manager (JSAM) will remain on the loading screen and fail to connect.  This issue is applicable only to PCS 8.1R11 and lower versions.

This issue is not applicable for PCS version 8.2R1 or higher.

     User-added image

Since the above end-user error message may appear for a variety of reasons, please enable Java Console logs on the end-user machine to verify if the following message is seen. If the below message occurs, then end-user is running into this issue. 
security: WARNING: The following resource is signed with a weak signature algorithm MD5withRSA and is 
treated as unsigned: XXXXXXXXX 
This algorithm is now disabled by the security property: jdk.jar.disabledAlgorithms=MD2, 
MD5, RSA keySize < 1024
The issue occurs due to the Java Applets being signed using MD5 signature algorithm on older versions (8.1R11 or lower) of PCS software and Java 8 update 131 introduces a new restriction on how MD5 signed JAR files are verified as mentioned in their release notes.
If you are an end-user and not the administrator of the PCS gateway device, please forward this article to the PCS administrator or IT team. 

To resolve this issue, upgrade the PCS gateway to 8.1R11.1, 8.1R12 or higher version of 8.1Rx PCS software if you wish to remain on 8.1Rx software branch. Alternatively, you may upgrade to the latest 8.2Rx software version to resolve this issue.  

Note: Prior to upgrading to latest 8.1Rx or latest 8.2Rx version, please review the following issue that impacts JSAM, Premier Java RDP and the Java Client Delivery applets KB40559 - JSAM and other Java applets fails to launch through the Pulse Connect Secure (PCS) device when using Encryption Strength 168-bit and greater after upgrading to 8.1R11.1 and above and 8.3R1


We strongly recommend to upgrade the PCS software version to fix this issue. However, if that is not possible, please use one of the below workarounds until the PCS software upgrade is completed. 
  • Downgrade Oracle Java JRE client version below update 131
  • Upload a Microsoft Authenticode certificate to the PCS gateway device and select the option to resign all PCS Applets
Related Links
Attachment 1 
Created ByK. Kitajima



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255