Fix (APAR):  PH02955

Status:  Fix

Release:  18.0.0.3

Operating System:  z/OS

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  1512881

Date: 2018-10-03

Abstract:  Unable to use SAF Keyring for collective SSH communication

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

ERROR DESCRIPTION:?                                             
A collective controller configured to use a SAF Keyring for     
its collective-wide SSH key may receive a                       
java.lang.ClassNotFoundException:                               
javax.xml.bind.DatatypeConverter during initialization.         
This class is used in the processing of a Keyring in the        
CollectiveHostAuthInfo configuration.                           
                                                                
The following is an example of the configuration using a SAF    
Keyring for Collective-wide SSH:                                
    <!-- BYO collective-wide SSH Key information. -->           
    <collectiveHostAuthInfo                                     
         safKeyring="safkeyring:///MIKE.KEYRING"                
         safCertificateLabel="Mike Label768" />                 
                                                                
The following is an example of the FFDC captured for this       
failure:                                                        
Stack Dump = java.lang.ClassNotFoundException:                  
javax.xml.bind.DatatypeConverter                                
 at java.lang.Class.forNameImpl(Native Method)                  
 at java.lang.Class.forName(Class.java:278)                     
 at                                                             
com.ibm.ws.collective.controller.config.internal.CollectiveH    
ostAuthInfoImpl.printBase64Binary(CollectiveHostAuthInfoImpl    
.java:1094)                                                     
 at                                                             
com.ibm.ws.collective.controller.config.internal.CollectiveH    
ostAuthInfoImpl.extractSAFSSHKeyPair(CollectiveHostAuthInfoI    
mpl.java:1057)                                                  
 at                                                             
com.ibm.ws.collective.controller.config.internal.CollectiveH    
ostAuthInfoImpl.validateKeyAccess(CollectiveHostAuthInfoImpl    
.java:384)                                                      
 at                                                             
com.ibm.ws.collective.controller.config.internal.CollectiveH    
ostAuthInfoImpl.processCollectiveHostAuthConfig(CollectiveHo    
stAuthInfoImpl.java:249)                                        
 at                                                             
com.ibm.ws.collective.controller.config.internal.CollectiveH    
ostAuthInfoImpl.activate(CollectiveHostAuthInfoImpl.java:178    
)                                                               
...                                                             

LOCAL FIX:?                                                     

PROBLEM SUMMARY:?

USERS AFFECTED:
 All users of IBM WebSphere Application
Server Liberty for z/OS

PROBLEM DESCRIPTION:
Unable to use SAF Keyring for
collective SSH communication

RECOMMENDATION:
None

A collective controller configured to use a SAF Keyring for its
collective-wide SSH key will be unable to communicate with other
servers in the collective.  A java.lang.ClassNotFoundException:
javax.xml.bind.DatatypeConverter will be seen during
initialization.  This class is used in the processing of a
Keyring in the CollectiveHostAuthInfo configuration.

The following is an example of the configuration using a SAF
Keyring for Collective-wide SSH:
<!-- BYO collective-wide SSH Key information. -->
<collectiveHostAuthInfo
safKeyring="safkeyring:///MIKE.KEYRING"
safCertificateLabel="Mike Label768" />

The following is an example of the FFDC captured for this
failure:
Stack Dump = java.lang.ClassNotFoundException:
javax.xml.bind.DatatypeConverter
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:278)
at
com.ibm.ws.collective.controller.config.internal.CollectiveHostA
uthInfoImpl.printBase64Binary(CollectiveHostAuthInfoImpl.java:10
94)
at
com.ibm.ws.collective.controller.config.internal.CollectiveHostA
uthInfoImpl.extractSAFSSHKeyPair(CollectiveHostAuthInfoImpl.java
:1057)
at
com.ibm.ws.collective.controller.config.internal.CollectiveHostA
uthInfoImpl.validateKeyAccess(CollectiveHostAuthInfoImpl.java:38
4)
at
com.ibm.ws.collective.controller.config.internal.CollectiveHostA
uthInfoImpl.processCollectiveHostAuthConfig(CollectiveHostAuthIn
foImpl.java:249)
at
com.ibm.ws.collective.controller.config.internal.CollectiveHostA
uthInfoImpl.activate(CollectiveHostAuthInfoImpl.java:178)
...

PROBLEM CONCLUSION:?                                            
Code was modified to successfully find the                      
javax.xml.bind.DatatypeConverter class on z/OS.                 
                                                                
The fix for this APAR is currently targeted for inclusion in fix
pack 18.0.0.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:  
NOTE: Mark with an X the:
1) Release the fix applies to
2) The Editions that apply
3) And then DELETE THIS NOTE

Fix applies to Editions:
Release 8.5
__ Application Server (BASE)
__ Network Deployment (ND)
__ Liberty Core

Install Fix to all WebSphere Virtual Enterprise 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 Knowledge 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 Knowledge 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: