PI42919: USER NOT ADDED TO USER ACCESS CONTROL LIST AND NO ERROR DISPLAYED WHEN USING BULK UPLOAD (.CSV)

Rational Asset Manager Fix Pack 3 (7.5.2.3) for 7.5.2
Rational Asset Manager Fix Pack 4 (7.5.2.4) for 7.5.2
Rational Asset Manager 7.5.3
Rational Asset Manager 7.5.3.1
Rational Asset Manager 7.5.3.2
Rational Asset Manager 7.5.3.3
Rational Asset Manager 7.5.4
Rational Asset Manager 7.5.4.1
Rational Asset Manager 7.5.4.2
Rational Asset Manager 7.5.4.3
Rational Asset Manager 7.5.4.4
Rational Asset Manager 7.5.4.5
Rational Asset Manager 7.5.4.6
Rational Asset Manager 7.5.4.7
Rational Asset Manager 7.5.4.9
Rational Asset Manager 7.5.4.8
Rational Asset Manager 7.5.4.10

APAR status

• Closed as fixed if next.

Error description

• When attempting to add users to the RAM user access control list
  (black/white list) using the bulk upload (.csv) feature, you may
  encounter an issue where users do not get added to the list and
  no error is displayed in the RAM web UI to indicate a failure,
  but then subsequently adding that user via manual add may be
  successful.
  
  This issue can occur when the validation check for a particular
  user returns multiple search results that match the criteria
  (i.e. e-mail address).  In this case, RAM can not determine
  which user is the correct one to be added, so the user is
  ignored and not added to the list.  However, an
  error/informational message should be displayed in the RAM web
  UI, to alert the administrator to the issue at hand.
  

Local fix

• To workaround the issue, you can manually add the user to the
  appropriate user access control list.
  
  Please contact IBM Support to obtain a test fix.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Server                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * This is slightly similar to a previously reported issue      *
  * (please see work                                             *
  * item 27576), where user with ID conflict was not added and   *
  * no error message was                                         *
  * displayed, which was reportedly resolved in ifix4l.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

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

Applicable component levels

• R752 PSY

     UP