Fix (APAR): PQ93459 Status: Fix Release: 5.1.1.2,5.1.1.1,5.1.1 Operating System: Multi-Platform Supersedes Fixes: CMVC Defect: PQ93459 Byte size of APAR: 16635 Date: 2005-02-24 Abstract: SSContextImpl.acceptSecContext() with an AbstractMethodError if SPNEGO is configured. Description/symptom of problem: This iFix is for Unix variants and Windows. The version of Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) shipped with WebSphere is not compatible with the interfaces provided by the IBM Java Generic Security Service (JGSS) included with JDK 1.4.2. This will cause code utilizing SPNEGO to fail with the following exception: java.lang.AbstractMethodError: com/ibm/security/jgss/mech/ spnego/SPNEGOMechFactory.getMechanismContext at com.ibm.security.jgss.GSSManagerImpl.createMechContext (GSSManagerImpl.java:4) at com.ibm.security.jgss.GSSContextImpl.acceptSecContext (GSSContextImpl.java:57) at com.ibm.security.jgss.GSSContextImpl.acceptSecContext (GSSContextImpl.java:124) ... The API GSSContextImpl.acceptSecContext() was reported in this APAR but others are likely to fail with the same error. One known Trust Association Interceptor (TAI) implementation that will fail is the IBM Software Services for WebSphere SPNEGO TAI. The following message will be seen with the stack trace above. [MM/DD/YY HH:MM:SS:XXX TMZ] 77f044f0 SpnegoTAI E com.ibm.issw.spnegoTAI.SpnegoTAI negotiateAndValidateEstablishedTrust() SPNEGO003: Unexpected exception: java.lang.AbstractMethodError: ... Other errors that may be seen in SystemOut.log: O [JGSS_DBG_UNMARSH] inner token len 1442 O [JGSS_DBG_PROV] Provider IBMJGSSProvider version 1.01 does not support mech 1.3.6.1.5.5.2 Directions to apply fix: NOTE: YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Fix Installer can be downloaded from the following link: http://www-3.ibm.com/software/webservers/appserv/support/index.html 1) Create temporary "fix" directory to store the jar file: UNIX: /tmp/WebSphere/fix Windows: c:\temp\WebSphere\fix 2) Copy jar file to the directory 3) Shutdown WebSphere 4) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix. 5) Restart WebSphere 6) The temp directory may be removed. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere 2) Follow the instructions that are packaged with the Fix Installer on how to uninstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Additional Information: