To configure the org chart portlet for anonymous access you must modify settings in the Org Chart preferences and also in the User Application WAR file. The steps are described in:
Go to
.Register and name a new instance of the OrgChartPortlet, for example, Public OrgChart.
Select the new instance, then go to the
tab.Set
to false, then click .Go to the
and modify the preferences as needed.Reference this instance of Org Chart from the Create or Detail portlets defined for anonymous access.
The org chart portlet relies on controls defined in the User Application WAR’s UIControlRegistry.xml file. By default, these controls require authentication. To allow guest access to the org chart portlet, you must set the authentication requirement to false in the definitions for the portal and vdm services in the WEB-INF\UIControlRegistry.xml file. Perform these instructions in a test environment before attempting them on a working version of the User Application. Make sure you backup your files before you begin.
To change the authentication requirements for the portal and vdm service definitions:
Open the User Application WAR and extract the contents.
Locate the UIControlRegistry.xml file in the WAR’s WEB-INF directory.
In the UIControlRegistry.xml file, locate the service definition for the portal service. It is shown below:
<service resultType="json" authenticated="true" config="false">
<key>portal</key> <classname>com.novell.srvprv.impl.servlet.service.PortalBridge
</classname> </service>
Change the value of
to .In the UIControlRegistry.xml file, locate the service definition for the vdm service. It is shown below:
<service resultType="json" authenticated="false" config="false"> <key>vdm</key> <classname>com.novell.srvprv.impl.servlet.service.VDMBridge
</classname> </service>
Change the value of
to .Save your changes.
Repackage the User Application WAR file.
To repackage the WAR file, you need to use the jar tool included with the JDK.
Note that the configupdate.sh script may fail after you manually add custom files to an IDM.war, if the WAR was created with the jar binary in /usr/bin/jar distributed in SLES 9. The error is:
DEBUG===WAR updating...java.util.zip.ZipException: invalid entry compressed size (expected 16176 but got 16177 bytes) at java.util.zip.ZipOutputStream.closeEntry(Unknown Source) at java.util.zip.ZipOutputStream.putNextEntry(Unknown Source)
To solve or prevent the problem, use a newer version of the jar tool to create the WAR, as in this example:/usr/lib/java/bin/jar -cvf IDM.war *
Deploy the updated WAR in your test environment.