Important Tech notes regarding IBM Java JCE certificate expiration 5/18/06

 Hi,
 
These technotes have been out for a while but Commerce Suite users and some
other applications may not be aware of them.  IBM has been busy today
supporting customers due to this problem.  They can affect any platform.

I have the new Jar files that replace the problem versions (IBM supplied,
unsupported) in case someone needs them.  Otherwise call your IBM Support.
 
 
1) In WebSphereR Application Server versions 4.0 and 5.0, the IBMR JavaT
Cryptography Extension (JCE) certificate will expire on 18 May 2006 at
21:59:19 GMT.

Notes: 

*       Application Server versions 5.0.2.5 and above are not affected
*       Application Server versions using SDK 1.4.1 and above are not
affected
*       Application Server - Express see reference in solution section

2) IBM Java Cryptography Extension (JCE) Expires on 18 May 2006 for
WebSphere Test Environment 5.0

3) IBM Java Cryptography Extension (JCE) embedded in the following IBM
products on OS/400 V5R2 or i5/OS V5R3 will expire on May 18, 2006. 

IBM WebSphere Business Integration Server Express V4.3.1.1 or earlier
IBM WebSphere Business Integration Server Express Plus V4.3.1.1 or earlier
IBM WebSphere Business Integration Server Express for Item Synchronization
V4.3.1.4 or earlier
IBM WebSphere Business Integration Server Express Plus for Item
Synchronization V4.3.1.4 or earlier

Error will be that the server instances can not start up. 

4) In WebSphereR Application Server for iSeriesT versions 4.0 and 5.0, the
IBMR 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     


Technote Links:

http://www-1.ibm.com/support/docview.wss?uid=swg21236118

http://www-1.ibm.com/support/docview.wss?uid=swg21237550

http://www-1.ibm.com/support/docview.wss?rs=1095&context=SSCL2Z&dc=DB520&uid
=swg21237179&loc=en_US&cs=utf-8&lang=en

http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q1=JCE+OS%2f4
00&uid=swg24012253&loc=en_US&cs=utf-8&lang=en


 

 
Kristen Henry
303-883-0144