IBM Support

PM91837: CSIV2 SESSION CACHE NOT TAKING GLOBALSECURITY AND SECURITYDOMAIN INTO ACCOUNT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • On the server where EJB call is received, LoginModules defined
    in Global Security are invoked rather than the LoginModules
    configured in the SecurityDomain.
    
    Problem Scenario:
    Configured Global Security Domain and a single Security Domain
    in a WebSphere Application Server cell with two clusters.
    One J2EE application (let's call it AppA) is deployed in one
    cluster and one application (AppB) is deployed in the other
    cluster. Both clusters are configured under the same
    SecurityDomain.
    
    Application AppA performs a remote EJB call to an EJB which
    resides in application AppB. The EJB is protected. The
    LoginModules are called incorrectly on the server where EJB
    call is received.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: CSIv2 session needs to be aware of      *
    *                      security domain if it is enabled.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Since EJB call for lookup object is carried out by using
    Administrative context, but EJBs which are owned by
    application are running under Application context, CSIv2
    session cache needs to distinguish these two contexts in order
    to use correct login context.
    

Problem conclusion

  • With this fix, in order to be aware of security context, CSIv2
    session cache uses security context information as a part of
    cache key
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.8, and 8.5.5.1.  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

    PM91837

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-25

  • Closed date

    2013-07-09

  • Last modified date

    2013-07-09

  • 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

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 January 2022