IBM Java Cryptography Extension (JCE) Expires on 18
May 2006
Downloadable files
Abstract
In WebSphere® Application Server for iSeries™ versions 4.0
and 5.0, the IBM® JCE certificate will expire on 18 May 2006 at 21:59:19
GMT.
Download Description
The signer certificate for the ibmjcefw.jar file is expiring on
5/18/2006. After that date, using WebSphere security, SSL, J2C security or
applications making calls to the IBM JSSE or IBM JCE will encounter
failures.
If you have any version of WebSphere Application Server V4.0 installed or
an earlier version than WebSphere Application Server V5.0 than V5.0.2.5
installed, the recommended solution is to move to the latest WebSphere
Application Server V5.0.2 fix pack.
Note: The jar file provided for download for the products listed below is
provided as is and is not a Program Temporary Fix (PTF). The end of
service date for V4.0 of the WebSphere Application Server release was 30
April 2005. PTFs are no longer provided for V4.0. The fix is contained in
fix pack V5.0.2.5, or higher, for the WebSphere Application Server V5.0
release and the problem does not exist in V5.1 and higher.
Releases affected:
WebSphere Application Server V4 Advanced Edition
WebSphere Application Server V4 Advanced Single Server Edition
WebSphere Application Server-Express V5.0, fix pack V5.0.2.4 or
earlier
WebSphere Application Server V5.0, fix pack V5.0.2.4 or earlier
WebSphere Application Server Network Deployment V5.0, fix pack
V5.0.2.4 or earlier
Prerequisites
WebSphere Application Server for iSeries V4 or WebSphere Application
Server for iSeries V5.0.2.4 or earlier.
Installation Instructions
Apply this fix to WebSphere Application Server for iSeries version 4.0
or WebSphere Application
Server for iSeries version 5.0.2.4 or earlier only. This problem does not
apply to WebSphere Application Server V5.0.2.5 or later.
The following list indicates the correct install root (was_install_root)
for each product which can be affected by this problem. Use this list to
determine the was_install_root or installation root directory in the
instructions below.
V4 Advanced Edition: /QIBM/ProdData/WebASAdv4
V4 Advanced Single Server Edition:
/QIBM/ProdData/WebASAEs4
V5 Express: /QIBM/ProdData/WebASE/ASE5
V5 Base: /QIBM/ProdData/WebAS5/Base
V5 Network Deployment: /QIBM/ProdData/WebAS5/ND
If you are using Version 5, run the versionInfo script as follows to
determine your fix pack level:
STRQSH
cd was_install_root/bin
versionInfo
If the Version displayed is 5.0.2.5 or higher, this problem does not apply
to you.
To apply the fix, repeat the following instructions for each installed
product on your system which is affected by this problem:
Download file WAS4OS400_ExpiringJceCertificateFix.jar to
a directory on your iSeries system.
Login to your iSeries system with a user profile that has
*ALLOBJ authority.
From and OS/400® command line, type "STRQSH" and press Enter
Change directory to the installation root directory of your WebSphere
Application server product. See the list above for the installation root.:
cd was_install_root
Extract the contents of file
WAS4OS400_ExpiringJceCertificateFix.jar. For example, if you
downloaded file WAS4OS400_ExpiringJceCertificateFix.jar to
/WASFixes/WAS4OS400_ExpiringJceCertificateFix.jar then do the
following:
jar -xf /WASFixes/WAS4OS400_ExpiringJceCertificateFix.jar
The jar command extracts the contents of the jar file to the current
directory. If no error occurs, the command completed successfully and the
jar file which fixes the problem is placed under the java/extlib
subdirectory..