PI69042: SECURITY CRYPTO JAR FAILED WITH NOT SIGNED BY A TRUSTED SIGNER ERROR AFTER UPGRADE

Fixes are available

APAR status

Closed as program error.

Error description

After WebSphere Application Server fix pack upgrade one of the
security crypto jar failed with not signed by a trusted signer
during wsadmin client invocation. These problem occurring on
Sun spark system due to JSSE/JCE provider list order.

./wsadmin.sh
WASX7023E: Error creating "SOAP" connection to host "localhost";
exception information:
com.ibm.websphere.management.exception.ConnectorNotAvailableExce
 ption:
[SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening
socket: java.net.SocketException: java.lang.SecurityException:
The Jar
(/opt/IBM/WebSphere/AppServer85/plugins/com.ibm.ws.security.cryp
to.jar) is not signed by a trusted signer;
targetException=java.lang.IllegalArgumentException: Error
opening socket: java.net.SocketException:
java.lang.SecurityException: The Jar
(/opt/IBM/WebSphere/AppServer85/plugins/com.ibm.ws.security.cryp
to.jar) is not signed by a trusted signer]
WASX7213I: This scripting client is not connected to a server
process; please refer to the log file
/opt/IBM/WebSphere/AppServer85/profiles/Dmgr01/logs/wsadmin.trac
eout for additional information.
WASX8011W: AdminTask object is not available.
WASX7029I: For help, enter: "$Help help"
wsadmin>

Local fix

Possible workaround to modify the
WAS_HOME/java/jre/lib/security/java.security with provider list

E.g.

security.provider.1=sun.security.provider.Sun
security.provider.2=com.ibm.security.jgss.IBMJGSSProvider
security.provider.3=com.ibm.crypto.fips.provider.IBMJCEFIPS
security.provider.4=com.ibm.crypto.provider.IBMJCE
:
:
security.provider.x=.......

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server on Sun Operating Systems when        *
*                  FIPS140-2 is enabled.                       *
****************************************************************
* PROBLEM DESCRIPTION: The Jar                                 *
*                      (/opt/IBM/WebSphere/AppServer85/plugins *
*                      /com.ibm.ws.security.cryp               *
*                      to.jar) is not signed by a trusted      *
*                      signer is shown.                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
There was a bug when WebSphere Application Server sets up
Java's provider order causing the jar verification error. The
issue happens on Sun OS when FIPS140-2 is enabled.

Problem conclusion

The bug was fixed in the code.

The fix for this APAR is currently targeted for inclusion in
fix packs 8.5.5.11 and 9.0.0.2.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PI69042
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-09-12
Closed date
2016-09-27
Last modified date
2016-10-04

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R850 PSY
UP
R900 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 May 2022

Tips

PI69042: SECURITY CRYPTO JAR FAILED WITH NOT SIGNED BY A TRUSTED SIGNER ERROR AFTER UPGRADE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?