PM64723: CAN NOT ADD CUSTOM REGISTRY USER AS RUN AS ROLE

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Can not add custom registry user as run as role
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0 and V8.5                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Users in a non-default file repository  *
  *                      are not listed in the search results    *
  *                      while assigning User RunAs Role.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a file repository is created and a paramter baseDirectory
  value is specified, virtual member manager ( VMM ) did not use
  the baseDirectory value to read the repository data.
  Therefore, it does not list the users from this repository in
  the search results while assigning User RunAs Role.
  

Problem conclusion

• To prevent this issue, changes are made to correctly use the
  baseDirectory value. Also if no baseDirectory is specified the
  data is read from the correct default location.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.5 and 8.5.0.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

• R800 PSY

     UP

• R850 PSY

     UP