Bookshelf Home | Contents | Index | Search | PDF

Security Guide for Siebel eBusiness Applications > Physical Deployment and Auditing > Securing Siebel Reports Server >

Configuring Reports Server for Security

---

Areas of Siebel Reports Server that can be configured for security, include:

Communication between the Siebel Web Client and Actuate Report Cast

This communication takes place during report viewing. When the Web Client communicates with Actuate Report Cast, a cookie that contains the encrypted Report Server login parameters is passed through the HTTP headers. Because the login parameters are encrypted, this part of the communication is secure by default.

However, the report itself is delivered in DHTML through Actuate Report Cast to the Siebel Web Client.

To make this part of the communications secure, enable SSL by setting the following parameter:

Actuate Server Network Protocol Name = HTTPS

For details on setting this parameter, refer to the postinstallation tasks described in the Siebel Reports Administration Guide.

Communication with the Application Object Manager

When report generation is initiated in the Actuate e.Reporting Server, this server uses Siebel Reports Server Access to communicate with the Application Object Manager. The e.Reporting Server establishes a separate session in the Object Manager and obtains data for report generation.

To secure this communication, set the desired encryption type (RSA or MSCRYTPO) for the Actuate Server Connect String parameter. For example:

Actuate Server Connect String = RSA

For details on setting this parameter, refer to the postinstallation tasks described in the Siebel Reports Administration Guide.

Bookshelf Home | Contents | Index | Search | PDF