IBM Content Navigator, Version 2.0.3

Disabling HTTPOnly settings for Java applets

WebSphere® Application Server Version 8 or later only. you must disable the HTTPOnly settings in WebSphere Application Server to enable IBM® Content Navigator to function properly. If you do not disable the HTTPOnly settings, features that use Java™ applets do not work.

About this task

When HTTPOnly settings are enabled in WebSphere Application Server, you cannot use the following features of IBM Content Navigator:

Sending links or attachments from the web client
Viewing documents in some viewers
File tracking
Deleting teamspaces by using the task manager feature

If you do not want to disable the HTTPOnly settings in WebSphere Application Server, you must take the following actions in the administration tool:

Remove the options to send links or attachments from the menus in the web client.
Configure a viewer map that does not use any viewers that require a Java applet, such as the IBM Daeja ViewONE Professional Edition Viewer and the Applet Viewer.
Ensure that file tracking is not enabled for the desktops in your environment.
Use the default method for deleting teamspaces, which removes the teamspace from the web client interface but does not delete the contents of the teamspace from the repository.

Highly Available Clusters If you plan to deploy IBM Content Navigator in a highly available cluster, you must complete the following steps for each node in the cluster.

Procedure

To disable the HTTPOnly settings in WebSphere Application Server:

Log in to the WebSphere Application Server administrative console.
Navigate to Servers > Server Types > Websphere Application servers and select the server where you want to deploy IBM Content Navigator.
Select Session Management > Enable cookies and then clear the Set session cookies to HTTPOnly to help prevent cross-site scripting attacks option.
Save the changes to the master configuration.
If you use IBM Content Navigator to access IBM FileNet® P8 repositories or an IBM Content Manager repository that is configured to use LTPA keys for authentication, you must also disable the HTTPOnly settings in the global settings:
1. Navigate to Security > Global secuirty > Authentication > Web and SIP security > Single sign-on (SSO).
2. Under General properties, clear the Set security cookies to HTTPOnly to help prevent cross-site scripting attacks option and click Apply.
3. Save the changes to the master configuration.
Restart the web application server for your changes to take effect.