i-fix Name: PK31448

Problem Summary: API : initworkspace tag doesn't work correctly

Detailed Problem Description:

The initworkspace tag does not set the authorisation correctly:

Initalizing the workspace, using the tag:

<wcm:initworkspace username="wpsadmin" password="wpsadmin" >

And then setting the explicit context via:

<wcm:setExplicitContext wcmWebAppPath="<%=webAppPath%>" wcmServletPath="<%=servletPath%>" path="<%=path%>" >

Can cause the following authorisation exception:

Exception caught processing request. Cause: IWKPY1017X: Unauthorised access on {57cb210041e70c7cbf8ebf51b318ac65, com.aptrix.pluto.site.Site} by {{anonymous portal user, anonymous_user, anonymous_user_id, en, Type: User}, 4, {false, {userAccess={}}, {editorAccess={}}, {managerAccess={}}, [anonymous_user%anonymous_user_id, all_users%all_users_group_id, anonymous_user%anonymous_user_id]}} - /Site


Problem Analysis:

The code used to calculate access to the Web Content Management Library is not correct, and may result in the system thinking that you are not authorised, when you do in fact have the correct credentials.

Failing Module: WCM - Web Content Management (General)

Problem Solution:

The access checks have been modified so that the access level will be calculated correctly for the API initworkspace tag.

Affected Users: All Users

Requisites:
   pre-requisite Portal Component: WCM 6.0.0.0 GA build 298.0
   pre-requisite interim fixes: PK30057

Platform Specific: No

Fix pack: This fix will be integrated into WPv6.0.0.1

Installation Steps:

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

- Create a temporary "fix" directory to store the jar file.
- Copy jar file to this directory.
- Shutdown WebSphere Portal.
- Ensure the pre-requisite fix(es) are installed.
- Follow the fix installation instructions that are packaged with the Portal Update Installer on how to install a fix.
  NOTE: If a pre-requisite fix is not installed, the Portal Update Installer will fail and will list the missing pre-requisite fix(es).
- Restart WebSphere Portal.
- Update the deployed remote rendering portlet:
   - Log in to Portal as the Portal Administrator
   - Navigate to: Administration / Portlet Management / Web Modules
   - Find and select the remote rendering portlet web module
   - Click the Update Portlet Icon to the right of the selected portlet
   - Select the updated portlet WAR file located in: [PortalServer]\installableApps
   - Click Next and Finish
- Log out of Portal for the changes to take effect.


Refer to the "Maintaining the cluster" section of the Portal Information Center for information on installing fixes in clustered environments while maintaining continuous availability of your Portal.

Note: 
If you are tryng to deploy the ifix on a horizontal cluster, Before you run the portal update installer, please take note of the cell name of your deployment manager. You can get the cell nameby going to the deployment manager machine, open <AppServerRoot>/profiles/<DeploymentManagerProfile>/config/cell/<CellName>/cell.xml 
and there will be a field indicating the cellname. (by default its called servernameCell01) 

For each node you are applying the ifix too, you need to: 
- Go into <PortalInstallRoot>/config/ 
- Open up wpconfig.properties 
- Search for the properties Field "CellName=" 
- Change it to point to the deployment manager's cellname. i.e. "CellName=DeploymentManagerCell" 

Un-Installation Steps:

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.

- Shutdown WebSphere Portal.
- Follow the instructions that are packaged with the Portal Update Installer on how to uninstall a fix.

- Restart WebSphere Portal.
- Update the deployed remote rendering portlet:
   - Log in to Portal as the Portal Administrator
   - Navigate to: Administration / Portlet Management / Web Modules
   - Find and select the remote rendering portlet web module
   - Click the Update Portlet Icon to the right of the selected portlet
   - Select the portlet WAR file located in: [PortalServer]\installableApps
   - Click Next and Finish
- Log out of Portal for the changes to take effect.

Refer to the "Maintaining the cluster" section of the Portal Information Center for information on installing fixes in clustered environments while maintaining continuous availability of your Portal.

Note: 
If you are tryng to deploy the ifix on a horizontal cluster, Before you run the portal update installer, please take note of the cell name of your deployment manager. You can get the cell nameby going to the deployment manager machine, open <AppServerRoot>/profiles/<DeploymentManagerProfile>/config/cell/<CellName>/cell.xml 
and there will be a field indicating the cellname. (by default its called servernameCell01) 

For each node you are applying the ifix too, you need to: 
- Go into <PortalInstallRoot>/config/ 
- Open up wpconfig.properties 
- Search for the properties Field "CellName=" 
- Change it to point to the deployment manager's cellname. i.e. "CellName=DeploymentManagerCell" 

DISCLAIMER:

This fix has received limited testing only and has not undergone IBM's complete quality assurance process. It is therefore recommended that it be tested in a testing environment before applying it to a working (authoring, production/live) system. You should always backup your data before installing a fix or fixpack.