Fixes are available
APAR status
Closed as program error.
Error description
Users without custom portlet instance are seeing data added by one user. And some users were able to create two custom portlet instances and, with these two instances they were able to add portlet preferences to the portlet definition, making them visible to all users. There is no stacktrace or error in the logs.
Local fix
1) delete the duplicate portlet instance for the user 2) delete the portlet preferences from the portlet definition.
Problem summary
Users are seeing portlet preferences added by other users that do not have the rights to add shared portlet preferences. The shared portlet preferences were visible for all users. This issue was caused by having two custom portlet instances for the same portlet - by design there should be only one. There is no stacktrace or error in the logs
Problem conclusion
Added an additional check just before storing the new portletinstance that would prevent duplicate user customizations from being created and also handled a database exception correctly that would allow normal users to add preferences to the portlet definition. Cleanup: 1) If your system already shows duplicate portlet instances, you would need to manually delete them with xmlaccess by exporting the page and removing setting the duplicate entries from action="update" to action="delete" and re-import the modified script. 2) Please go to the manage portlets portlet and pick the portlet (definition) for the portletinstance that you removed in1) and verify and/or remove the unwanted preferences. Note that some portlets store the data in binary format such that you may not be able to identify single individual preferences. Manual Steps: None Failing Module(s): Database Engine: Page Assembly Affected Users: All users Version Information: Portal Version(s): 6.0.1.5 Pre-Requisite(s): PK93166 PK80909 Co-Requisite(s): --- Portal Version(s): 6.0.1.6 Pre-Requisite(s): PK93166 Co-Requisite(s): --- Portal Version(s): 6.1.0.1 Pre-Requisite(s): PK80909 PK93166 Co-Requisite(s): --- Portal Version(s): 6.1.0.2 Pre-Requisite(s): PK93166 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 ?apar=PK97053&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 number
PK97053
Reported component name
WEBSPHERE PORTA
Reported component ID
5724E7699
Reported release
60J
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-24
Closed date
2009-10-13
Last modified date
2009-10-13
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
5724E7699
Applicable component levels
R60J PSY
UP
R60K PSY
UP
R61A PSY
UP
R61B PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1.5","Edition":"","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]
Document Information
Modified date:
11 February 2022