PH25204: After server is restarted, SpnegoTokenHelper API may fail due to the lack of Kerberos credential.

APAR status

• Closed as program error.

Error description

• server restart issue
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  who configured SPNEGO Single Sign-ON (SSO)  *
  ****************************************************************
  * PROBLEM DESCRIPTION: SpnegoTokenHelper APIs may fail after   *
  *                      server restart due to the lack of       *
  *                      Kerberos credentials.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the server restarts, the server cache that stores Kerberos
  credentials becomes empty. However, the client browser still
  caches ltpaToken from the server prior to the restart.  This
  ltpaToken was associated with Kerberos credentials that used to
  be stored in the server cache. As a result, operations
  that requires Kerberos credentials fail until the ltpaToken
  expires that finally triggers the new SPNEGO SSO.
  

Problem conclusion

• This apar introduces a new custom property below.
  
  Custom property:
  com.ibm.websphere.security.spnego.includeCustomCacheKeyInSubje
  ct
  Value: true (default is false)
  
  When it is set to true, WebSphere creates a LtpaToken that
  includes a custom cache key derived from the associated Kerberos
  credentials.
  
  When WebSphere receives a LtpaToken with this custom cache key,
  and if it does not have a cache hit, the server initiates a new
  Spnego SSO to obtain a new Kerberos credentials to provide
  uninterrupted service.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.19 and 9.0.5.6. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  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

• R850 PSY

     UP

• R900 PSY

     UP