Cognos ReportNetTM Installation and Configuration Guide

Chapter 4: Configuring ReportNet
3. In the Properties window, change the default values by clicking the Value box and then
selecting the appropriate value:
• If you do not want to store the CSKs locally, under CSK settings, change Store
symmetric key locally to False. Then change the Common symmetric key store
location to the key store location of the Content Manager computer.
When Store symmetric key locally is False, the key must be retrieved from Content
Manager.
• If you want the computers at both ends of a transmission to prove their identity, under
SSL Settings, change Use mutual authentication to True.
We recommend that you do not change the Use confidentiality setting. Set this
property to true to ensure all transmissions are encrypted.
• If you want to change the confidentiality algorithm, under Advanced algorithm
settings, change Confidentiality algorithm to the other 40-bit key value.
If you select and try to save an algorithm that does not use a 40-bit key, you will receive
an error message. These other algorithms are reserved for use with other cryptographic
providers. For more information, see the Enhanced Encryption Module for OpenSSL
Installation Guide or the Enhanced Encryption Module for Entrust Installation Guide.
4. From the File menu, click Save.
After you configure the cryptographic provider, passwords in your configuration and any data
you create are encrypted.
Steps for Cryptographic Provider Settings
1. Start Cognos Configuration.
2. In the Explorer window, under Security, Cryptography, click Cognos.
• If you want to use a third-party certificate authority, under Certificate Authority
settings, change Use third party CA to True.
• If you want to change the location of the signing keys, under Signing key settings,
change the Signing key store location property to the new location.
• If you want to change the location of the encryption keys, under Encryption key
settings, change Encryption key store location to the new location.
3. From the File menu, click Save.
If you use a third-party Certificate Authority (CA) server, you must now configure ReportNet to
use the CA.
Configure the SSL Protocol
You can configure ReportNet components to use the Secure Sockets Layer (SSL) protocol for
• internal connections only
• external connections only
• internal and external connections
• connections to local and remote log servers.
If you configure SSL only for internal connections, ReportNet components on the local computer
communicate using this protocol. The dispatcher listens for secure connections on a different
port than for remote, http requests. Therefore, you must configure two dispatcher URIs.
If you configure SSL only for external connections, communications from remote ReportNet
components to the local computer use the SSL protocol. You must configure the dispatcher to
listen for secure, remote requests on a different port than local, http requests.
If you configure SSL for all connections, the dispatcher can use the same port for internal and
external connections. Similarly, if you do not use SSL for local or remote communication, the
dispatcher can use the same port for all communications.
You must also update the Content Manager URI, SDK URI, and Gateway URI to use SSL, if
required.
Installation and Configuration Guide 47