PK79235: Invalid action identifier caused by wrong user session key

6.1.0.2 Download: WebSphere Portal and Web Content Management V6.1, fix pack 2
6.1.0.3 Download: WebSphere Portal and WCM V6.1 fix pack 3, 6.1.5 feature pack
6.1.0.4 Download: WebSphere Portal and WCM V6.1.0 fix pack 4 & 6.1.5 fix pack 1
6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5
6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6

APAR status

• Closed as program error.

Error description

• Since WP 6.1.0, the component which is responsible for creating
  and validating action identifiers is initialized lazily via a
  factory. The factory stores the initialized handler instance in
  the request using a request attribute (i.e. it uses the request
  as a cache). In case of a cache miss, a new action ID handler is
  created and initialized accordingly. In some cases, if a URL is
  created from within a portlet, the request attribute holding the
  handler is not visible causing the handler factory to create and
  initialize a new handler. However if this occurs during the
  render phase, the initialization will be based on the
  application-specific session causing the generated action
  identifiers to be invalid.
  
  Problem solution:
  This fix makes sure that the initialized action ID handler which
  is cached in the request is accessible for all portlets to avoid
  invalid action identifiers.
  
  Releases to be built:
  wp610.base, wp6101.base
  

Local fix

• na
  

Problem summary

• Since WP 6.1.0, the component which is responsible for
  creating and validating action identifiers is initialized lazily
  via a factory. The factory stores the initialized handler
  instance in the request using a request attribute (i.e. it uses
  the request as a cache). In case of a cache miss, a new action
  ID handler is created and initialized accordingly. In some
  cases, if a URL is created from within a portlet, the request
  attribute holding the handler is not visible causing the handler
  factory to create and initialize a new handler. However if this
  occurs during the render phase, the initialization will be based
  on the application-specific session causing the generated action
  identifiers to be invalid.
  

Problem conclusion

• This fix makes sure that the initialized action ID handler which
  is cached in the request is accessible for all portlets to avoid
  invalid action identifiers.
  
  Failing Module(s):
     Portal Access Control
  
  Affected Users:
     All users
  
  Version Information:
      Portal Version(s): 6.1.0.1
       Pre-Requisite(s):
        Co-Requisite(s): ---
  
  Platform Specific:
     This fix applies to all platforms.
  
  A fix is available from Fix Central:
  
  http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
  r?apar=PK79235&productid=WebSphere%20Portal&brandid=5
  
  You may need to type or paste the complete address into your Web
  browser.
  

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 PORTA

• Fixed component ID

  5724E7600

Applicable component levels

• R61A PSY

     UP