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

Configuring Siebel Reports Server for Security

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

• Communication between Siebel Web Client and Actuate Active Portal
• Communication with the AOM

Communication Between Siebel Web Client and Actuate Active Portal

This communication takes place during report viewing. When the Siebel Web Client communicates with Actuate Active Portal, a cookie that contains the encrypted Reports Server login parameters is passed through the HTTP headers. Because the login parameters are encrypted, this part of the communication is secure by default. The report itself is delivered in DHTML through Actuate Active Portal 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, see the postinstallation tasks described in the Siebel Installation Guide for the operating system you are using.

For more information about cookies and Siebel applications, see Cookies and Siebel Applications.

Communication with the AOM

Report generation is initiated through the Siebel Reports Adapter for Actuate (which is part of the Siebel Web Services Framework), by using a SOAP call to Active Portal. A connection is established to the Actuate iServer using the supplied user credentials from the Siebel application. The iServer establishes a separate session to the Application Object Manager to obtain data for report generation. This communication is encrypted.

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, see the postinstallation tasks described in the Siebel Installation Guide for the operating system you are using.