PH39881: File Repository user able to login after failed user account creation on managed node.

APAR status

• Closed as program error.

Error description

• When the request to programmatically create a File Repository
  user is sent to a managed node instead of the Deployment
  Manager, the request
  will fail as expected, with the following message:
  
  CWWIM4508E  Virtual member manager failed to write to the
  '<profile_root>/config/cells/<cell_name>/fileRegistry.xml' file:
  'CWWIM6009E All updates must be performed at the deployment
  manager and not at a managed node.'
  
  However, after the attempt fails, the user is able to login into
  the managed node until the node or server is restarted.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  making changes to File Repository users.    *
  ****************************************************************
  * PROBLEM DESCRIPTION: A File Repository user able to login    *
  *                      after failed user account creation on a *
  *                      managed node.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the request to programmatically create a File Repository
  user is sent to a managed node (such as a create user request on
  the administrative console or wsadmin) instead of the Deployment
  Manager, the request will fail as expected, with the following
  message:
  CWWIM4508E  Virtual member manager failed to write to the
  '<profile_root>/config/cells/<cell_name>/fileRegistry.xml'
  file:
  'CWWIM6009E All updates must be performed at the deployment
  manager and not at a managed node.'
  However, after the create attempt fails, the user is able to
  login into the managed node until the node or server is
  restarted. Another file repository update synchronized to the
  node will also remove the failed user.
  

Problem conclusion

• The code was corrected to do the permissions verification first,
  before updating the runtime list of users.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.22 and 9.0.5.11. 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