PH42057: ERROR WHEN DISABLING CUSTOM PASSWORD ENCRYPTION

APAR status

• Closed as program error.

Error description

• Customer installed WAS9.0.5.9 , so they set custom property "co
  m.ibm.wsspi.security.crypto.customPasswordEncryptionEnabled=fal
  se".
  dmgr did not start with following error message.
  ---
  [21/10/05 13:17:25:171 JST] 00000001 ORBRas E
  com.ibm.ws.orbimpl.transport.WSTransport createServerSocket
  P=445009:O=0:CT ORBX0390E: ?????????????????? ?? = [
  org.omg.CORBA.INTERNAL:
  CAUGHT_EXCEPTION_WHILE_CONFIGURING_SSL_SERVER_SOCKET,
  Exception=com.ibm.websphere.ssl.SSLException:
  java.lang.IllegalArgumentException: No key store specified and
  no hardware crypto defined vmcid: 0x49421000 minor code: 77
  completed: No - received while attempting to open server socket
  on port 9403 ]?
  ---
  
  Customer have only placed the jar file in ${WAS_INSTALL_ROOT}
  /classes.
  The jar file name is sys230CustomPasswordEncryption.jar.
  It iclude the class
  :com.ibm.wsspi.security.crypto.CustomPasswordEncryptionImpl.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: After upgrading to WebSphere            *
  *                      Application Server 9.0.5.9 through      *
  *                      9.0.5.11 it's imposible to remove       *
  *                      custom password encryption since the    *
  *                      server won't start again.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  After upgrading to WebSphere
  Application Server 9.0.5.9 it's
  imposible to remove custom password
  encryption since the server won't
  start again.
  

Problem conclusion

• The code has been revised and updated to address this problem.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.22 and 9.0.5.12. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels