PI46937: Security identity not propagated from batchManagerZos to batch exectuor in multi-server environment causes JobSecurityException

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.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• The security identity of the user who invokes
  batchManagerZos is supposed to be used as the RunAs identity
  for he batch job running in the Liberty server.  In a
  multi-server batch environment, the batchManagerZos identity
  fails to get propagated over JMS from the batch dispatcher
  to the batch exectuor, where the job ultimately runs.
  Instead, the unauthenticated user is propagated, and the
  batch job runs under the unauthenticated user.  This may
  result in a JobSecurityException.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile for z/OS             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Security identity not propagated from   *
  *                      batchManagerZos to batch exectuor in    *
  *                      multi-server environment causes         *
  *                      JobSecurityException                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The security identity of the user who invokes batchManagerZos is
  supposed to be used as the RunAs identity for the batch job
  running in the Liberty server.  In a multi-server batch
  environment, the batchManagerZos identity fails to be propagated
  over JMS from the batch dispatcher to the batch exectuor where
  the job ultimately runs.  Instead, the unauthenticated user is
  propagated, and the batch job runs under the unauthenticated
  user.  This may result in a JobSecurityException.
  

Problem conclusion

• The RunAs Subject for the batchManagerZos client identity was
  updated to contain the appropriate credentials so that the
  identity can be propagated over JMS.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.8.  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

  LIBERTY PROF -

• Fixed component ID

  5655W6514

Applicable component levels

• R850 PSY

     UP