PM89817: SUPPORT FOR CUSTOM HASHING MECHANISM FOR HASHING THE PASSWORDS IN FILE REGISTRY

8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

APAR status

• Closed as new function.

Error description

• Currently VMM uses SHA-1 hashing mechanism to hash the
  password while creating/login users in file registry. So if
  some one wants to hash a password with its own hahsing
  mechanism VMM doesnt allowed that.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5 virtual member manager (VMM)    *
  ****************************************************************
  * PROBLEM DESCRIPTION: File registry repository doesn't        *
  *                      support any custom hashing mechanism    *
  *                      for the passwords.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Currently VMM uses SHA-1 hashing mechanism to hash the
  password while creating/login users in file registry. So if
  someone wants to hash a password with their own hashing
  mechanism VMM does not allow that.
  

Problem conclusion

• VMM now provides a mechanism through which custom hashing
  algorithm can be used for hashing the password apart from the
  default hashing mechanism.
  
  To use the custom hashing support these steps need to be
  followed:
  
  1. To support custom hashing algorithm VMM provides an
  interface named ICustomHashAlgo that you need to implement.
  2. You have to set a new custom property
  customHashImplClassName to provide the name of the
  implementation class.
  
  This implementation class will then be used at runtime for
  hashing the passwords of the user.
  
  $AdminTask setIdMgrCustomProperty {-id <repository_id>  -name
  customHashImplClassName -value <full_impl_class_name>}
  
  Here "repository_id " is the id of the file registry
  configured in VMM. "full_impl_class_name" is the name of the
  implementation class.
  Also save the configuration after running the previous command
  using:
  $AdminConfig save
  
  For example:
  $AdminTask setIdMgrCustomProperty {-id fileRepo  -name
  customHashImplClassName -value "com.ibm.custom.customImplClass"}
  
  3. The custom hashing algorithm implementation class will be
  loaded at runtime from the jar under which your
  implementation class is bundled which should be present under
  the WAS_HOME/lib/ext folder.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.1.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

• R850 PSY

     UP