To ensure a higher degree of security, you can disable the mechanism that transfers the Cognos 8 passport ID as a URL parameter between users' browsers and the Cognos 8 gateway. You can do this only when single signon is implemented between the users' browsers and Cognos 8, and, if applicable, Cognos Series 7, independently of Portal Services.
By default, Portal Services re-creates the active credential cookie in the user's browser by passing the passport ID as a URL parameter. If single signon is not implemented, then when portal users interact with Cognos portlets, they are authenticated both in the portal and in Cognos 8. The portal, not the user's browser, maintains the active credential token generated by Cognos 8. In some situations, for example when you want to see a report in a Cognos portlet, a direct connection between the user's browser and the Cognos 8 gateway must be established. This may become a security risk because a valid Cognos 8 passport ID appears in some log files. The same applies when Cognos 8 is integrated with Cognos Series 7 and the active credential is passed as a URL parameter.
In Cognos Connection, in the upper-right corner, click Launch, Cognos Administration.
On the Configuration tab, click Dispatchers and Services.
Click the dispatcher you want.
For the PresentationService, in the Actions column, click the set properties button.
Click the Settings tab.
For the Environment category, next to Advanced settings, click the Edit link.
Select the Override the settings acquired from the parent entry check box.
In the Parameter column, type the parameter names:
This parameter controls the transfer of the Cognos 8 passport ID as a URL parameter. When set to 0, it stops the transfer.
Controls the transfer of the Cognos Series 7 ticket ID as a URL parameter. When set to 0, it stops the transfer.
The parameters are case sensitive.
In the Value column, type 0 for each parameter.
Click OK.
Click OK again.
Click the Configuration link next to the path at the top of the page.
You return to the list of dispatchers.
If you have more than one dispatcher configured, perform steps 3 to 12 for each remaining dispatcher.