Fix (APAR):  PI25681

Status:  Fix

Release:  8.5.5.3

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  299973

Date: 2014-11-03

Abstract:  remove export packages of the org.apache.commons.codec from the com.ibm.ws.security.oidc.client.jar

Description/symptom of problem:  
PI25681 resolves the following problem:

ERROR DESCRIPTION:                                              
The application cannot load its own version of the              
org.apache.commons.codec.binary.Base64 class that is packaged   
within the application. The new WAS_HOME/plugins/               
com.ibm.ws.security.oidc.client_1.0.0.jar shipped               
with fix pack v8.5.5.3 is loaded instead. This causes the       
application failed with NoSuchMethodError:                      
                                                                
java.lang.NoSuchMethodError:                                    
org/apache/commons/codec/binary/Base64.isBase64(Ljava/lang/Strin
g;)                                                             

LOCAL FIX:                                                      
Change the classloader mode for the WAR to parent_last.         

PROBLEM SUMMARY

USERS AFFECTED:
 All users of IBM WebSphere Application
Server

PROBLEM DESCRIPTION:
Export packages in
com.ibm.ws.security.oidc.client_1.0.0.j
ar may cause application
initialization failures

RECOMMENDATION:
 Install a fix pack that contains this
APAR.

An application that has packaged org.apache.commons packages
with its application may experience an initializion failure.
Setting the PARENT_LAST classloader policy can illeviate the
problem.

PROBLEM CONCLUSION:                                             
In com.ibm.ws.security.oidc.client_1.0.0.jar,                   
org.apache.commons packages are exported for use by             
com.ibm.ws.security.openid20.client.jar.  These exports         
may cause applications that package their own version of the    
org.apache.commons.code packages to fail to initialize.         
                                                                
The org.apache.commons.codec, org.apache.commons.codec.binary,  
and org.apache.commons.codec.net packages are removed from      
com.ibm.ws.security.oidc.client_1.0.0.jar.  These packages are  
now bundled in both com.ibm.ws.security.oidc.client_1.0.0.jar   
and com.ibm.ws.security.openid20.client.jar.                    
                                                                
The fix for this APAR is currently targeted for inclusion in    
fix pack 8.5.5.4.  Please refer to the Recommended Updates      
page for delivery information:                                  
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  Fix applies to Editions:
Release 8.0
_x_ Application Server (Express or BASE)
_x_ Network Deployment (ND)
__ Edge Components
__ Developer

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required.

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before applying the iFixes.  Restart WebSphere Application Server after applying the iFixes.

Directions to remove fix:  

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before removing the iFixes.  Restart WebSphere Application Server after removing the iFixes.

Directions to re-apply fix:  
1) Shutdown WebSphere Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: