Name: PK40343
=============
 
Summary:
   Incorrect 
 
Problem Description:
      Portal will incorrectly offer personalize mode for JSR 168 portlets when a user has one of the
      following role combinations set for page and portlet and storing portlet settings will lead
      to read only exceptions:
      editor@page & editor@portlet, privileged user, editor@page & editor@portlet, editor@page, privileged user, editor@portlet
      
      When storing settings with these permission combinations, a ReadOnlyException will occur in the log, like this one:
      
      [17.07.06 14:58:37:922 CEST] 00000040 ServletWrappe E SRVE0014E: Uncaught service() exception root cause PrefSamplePortlet: javax.portlet.ReadOnlyException: Preference attribute called document may not be modified 
      
      Additionally, when the user has privileged user, editor role for both page and portlet, the edit
      shared settings mode will actually only store personalized settings.
      
      IBM API portlets:
      When a user with privileged user role for both page and portlet customizes the page (e.g. by
      changing portlet settings or the page layout) and later is promoted to privileged user, editor
      for both page and portlet, the edit shared settings mode is displayed, by storing will be for
      private settings only (instead, personalize should display). If the user is promoted to privileged user, editor of the page and to editor role (only) of the portlet, then edit shared
      settings is displayed, but clicking the link results in a 404 error message from the server; the
      log will display an exception such as com.ibm.wps.command.MissingAccessRightsException: EJPEC0378E: ...
   
 
Problem Solution:
      The scoping of PortletEntities for edit shared settings was fixed in the portlet container code to use the shared instance; the code checking the permissions for the various portlet modes was changed to respond with the correct portlet modes.
      
 
Failing Module(s):
   Engine: Page Assembly
   Portlet Container
 
Affected Users:
   All users
 
Version Information:
    Portal Version(s): 6.0.0.0
     Pre-Requisite(s): PK30893 
      Co-Requisite(s): ---
 
Platform Specific:
   This fix applies to all platforms.
 
Installation:
   NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
          The Portal Update Installer can be downloaded from the following link:
          http://www.ibm.com/software/genservers/portal/support
 
   1. Create temporary "fix" directory to store the jar file.
   2. Copy jar file to this directory.
   3. Shutdown WebSphere Portal.
   4. Follow the fix installation instructions that are packaged with
      the Portal Update Installer on how to install the fix.
   5. Restart WebSphere Portal.
   6. The temporary directory may be removed.
 
Un-Installation:
   NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE
          A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
          YOU MAY REAPPLY ANY REMOVED FIX.
 
   1. Shutdown WebSphere Portal.
   2. Follow the instructions that are packaged with the
      Portal Update Installer on how to uninstall the fix.
   3. Restart WebSphere Portal.