PK81126: CONTAINER-MANAGED ALIAS WILL PREVENT THREAD IDENTITY FOR BEING USED FOR AUTHENTICATION CAUSING JAVA.LANG.ILLEGALSTATEEXCEPTION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In V7.0, container-managed alias will prevent thread identity
  for being used for authentication causing
  java.lang.IllegalStateException as can be seen when connecting
  to J2C datasources:
  
  java.lang.IllegalStateException:
  ThreadIdentitySecurityHelper.beforeGettingConnection() detected
  Subject with no credentials
  
  The root of the problem seems to be in a method
  getAliasToFinalize()
  which checks for container-managed alias or
  DefaultPrincipalMapping alias from res-ref. This method is new
  for v7 and it replaced the previous way of checking for the same
  condition by verifying that Subject's private credentials are
  not present.  In this case, there is no private credentials but
  the method returns a not null alias.
  
  For the reference, setting up the DefaultPrincipalMapping alias
  in res-ref or deprecated container-managed alias will prevent
  thread identity for being used for authentication, and a check
  for those conditions is stronger now than it used to be in v6.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Application Server   *
  *                  V7.0 for z/OS                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Thread identity function cannot be      *
  *                      correctly enabled when a                *
  *                      container-manager alias is set to an    *
  *                      empty string.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The following exception may be logged when an application
  attempts to get connection using thread identity function while
  a container-managed alias is set to an empty string:
  java.lang.IllegalStateException:
  ThreadIdentitySecurityHelper.beforeGettingConnection() detected
  Subject with no credentials
  

Problem conclusion

• Thread identity function will check for both NULL and empty
  container-managed alias when deciding if conditions for
  enabling thread identity are fulfilled.
  
  APAR PK81126 is currently targeted for inclusion in Service
  Level (Fix Pack) 7.0.0.4 of WebSphere Application Server V7.0
  for z/OS.
  
  Please refer to URL:
  //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack availability.
  

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

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R700 PSY UK46315

     UP09/05/16 P F905

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.