IBM Support

PM30025: CUSTOM CREDENTIAL OR KERBEROS TOKEN MIGHT BE LOST WHEN A SUBJECT IS REFRESHED

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
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

  • When using a TAI that initially sets the security context
    successfully, then when the LTPA token nears expiration, it is
    possible that this error could occur, due to a failed attempt by
    the Application Server to refresh the ssoToken:
    org.omg.CORBA.NO_PERMISSION: SecurityName is null  vmcid:
    0x49424000  minor code: 300  completed: No
    at
    com.ibm.ISecurityLocalObjectBaseL13Impl.PrincipalAuthFailReason.
    map_auth_fail_to_minor_code(PrincipalAuthFailReason.java:88)
    at
    com.ibm.ISecurityLocalObjectBaseL13Impl.CSIServerRIBase.authenti
    cateSecurityTokens(CSIServerRIBase.java:4488)
    at
    com.ibm.ISecurityLocalObjectBaseL13Impl.CSIServerRI.receive_requ
    est(CSIServerRI.java:615)
    at
    com.ibm.rmi.pi.InterceptorManager.invokeInterceptor(InterceptorM
    anager.java:624)
    at
    com.ibm.rmi.pi.InterceptorManager.iterateServerInterceptors(Inte
    rceptorManager.java:524)
    at
    com.ibm.rmi.pi.InterceptorManager.iterateReceiveRequest(Intercep
    torManager.java:770)
    at
    com.ibm.CORBA.poa.POAServerDelegate.dispatchToServant(POAServerD
    elegate.java:398)
    at
    com.ibm.CORBA.poa.POAServerDelegate.internalDispatch(POAServerDe
    legate.java:334)
    at
    com.ibm.CORBA.poa.POAServerDelegate.dispatch(POAServerDelegate.j
    ava:256)
    at com.ibm.rmi.iiop.ORB.process(ORB.java:513)
    at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)
    at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2841)
    at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2714)
    at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
    at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: A custom credential or kerberos token   *
    *                      might be lost during refreshing Subject *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using a Trust Association Interceptor (TAI) or a custom
    login module that initially constructs a Subject
    successfully, when the LTPA token nears expiration, it is
    possible to get a CORBA.NO_PERMISSION error from a
    downstream server or some error from an application which used
    to consume the custom token.  This is due to a failed attempt
    by the Application Server to refresh the Subject:
    
    There was an APAR PK93018 which intended to resolve this
    issue. However, a CORBA.NO_PERMISSION exception with "within
    cushion window" message was thrown during RMI call even a
    Subject is still valid. This issue was introduced by a code
    defect of PK93018.
    

Problem conclusion

  • With this fix, a WSLoginFailedException is thrown if one of
    credentials is being expired. This exception forces either
    TAI or custom login module to login again. With this, a custom
    token will be placed in a Subject.
    Along with this fix, CORBA.NO_PERMISSION error which was
    introduced by PK93018 is removed.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.39 and 7.0.0.19. 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

    PM30025

  • 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

    2011-01-07

  • Closed date

    2011-04-18

  • Last modified date

    2011-04-18

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM30025

Modified date: 18 April 2011