IBM Support

PK97491: TOKENEXPIREDEXCEPTION ON WEBSPHERE APPLICATION SERVER V7

Fixes are available

7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • [10/8/08 20:47:20:562 CEST] 00000413 ExceptionUtil E
    CNTR0020E: EJB threw an unexpected (non-declared) exception
    during invocation of method
    "transactionSupportsActivitySessionNotSupported" on bean
    "BeanId(RunAJob_Modu
    leApp#RunAJob_ModuleEJB.jar#Module, null)". Exception data:
    com.ibm.websphere.security.auth.TokenExpiredException: Token
    expiration Date: Wed Oct 08 20:47:04 CEST 2008, current Date:
    Wed Oct 08 20:47:18 CEST 2008
            at
    com.ibm.ws.security.ltpa.LTPAToken.isValid(LTPAToken.java:248)
            at
    com.ibm.ws.security.ltpa.LTPAServerObject.validateToken(LTPAServ
    erObject.java:1004)
            at
    com.ibm.ws.security.ltpa.LTPAServerObject.validateToken(LTPAServ
    erObject.java:901)
            at
    com.ibm.ws.security.ltpa.LTPAServerObject.validateToken(LTPAServ
    erObject.java:870)
            at
    com.ibm.ws.security.ltpa.LTPAServerObject.validate(LTPAServerObj
    ect.java:1234)
            at
    com.ibm.ws.security.server.lm.ltpaLoginModule.login(ltpaLoginMod
    ule.java:607)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
            at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:79)
            at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:618)
            at
    javax.security.auth.login.LoginContext.invoke(LoginContext.java:
    795)
            at
    javax.security.auth.login.LoginContext.access$000(LoginContext.j
    ava:209)
            at
    javax.security.auth.login.LoginContext$4.run(LoginContext.java:7
    09)
            at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:246)
            at
    javax.security.auth.login.LoginContext.invokePriv(LoginContext.j
    ava:706)
            at
    javax.security.auth.login.LoginContext.login(LoginContext.java:6
    03)
            at
    com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHel
    per.java:188)
            at
    com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManager
    Impl.java:2918)
            at
    com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManager
    Impl.java:2706)
            at
    com.ibm.ISecurityLocalObjectTokenBaseImpl.WSSecurityContextLTPAI
    mpl.acceptSecContext(WSSecurityContextLTPAImpl.java:304)
            at
    com.ibm.ISecurityLocalObjectTokenBaseImpl.WSSecurityContextLTPAI
    mpl.acceptSecContext(WSSecurityContextLTPAImpl.java:222)
            at
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server v7                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When executing a request intended to    *
    *                      run longer than the LTPA timeout, and   *
    *                      the refreshIfExpired flag has been      *
    *                      enabled, users may receive a            *
    *                      TokenExpiredException.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    WebSphere Application Server was not honoring the
    refreshIfExpired
    flag and therefore was not refreshing the LTPA token in the
    subject.
    

Problem conclusion

  • WebSphere Application Server Feature Pack functionality has
    been modified to properly refresh the LTPA token
    in the subject.
    
    Because WebSphere Application Server supports Kerberos
    starting with v7, the refresh of the subject may now include
    an attempt to refresh the Kerberos token. This APAR introduces
    a new custom property that will allow administrators to make
    decisions regarding intended behavior when the Kerberos token
    in the subject has reached it's expiration time. When the
    property
    
    com.ibm.wsspi.wssecurity.kerberos.failAuthForExpiredKerberosToke
    n
    
    is set to a value of true, and the Kerberos token in the
    subject has expired, and WebSphere Application Server is
    unable to refresh the token, authentication will fail for the
    request. If the value is false (which is the default), an
    expired Kerberos token will not fail the authentication for
    the request.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.9.  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 number

    PK97491

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-09-30

  • Closed date

    2009-10-29

  • Last modified date

    2009-10-29

  • 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

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021