Page History

...

When installing a new server, a communication security key is transferred to the new server. To ensure secure transfer of the key, see Securing communication key transfer to a new server on page 48.

Anchor
ConfiguringasecuredPrecisesystem ConfiguringasecuredPrecisesystem

Configuring a secured Precise system

...

1. Log in to the Main Precise FocalPoint.
2. Run the following command from the <Precise_root> folder:
   • Windows
     infra\bin\psin_cli.bat
-i3-user<user_name>
{-i3-encrypted-password<encrypted_password>|-i3-clear-password<clear_password>}
-action communication-key-change
-type aes
   • UNIX
     ./infra/bin/psin_cli.sh
-i3-user<user_name>
{-i3-encrypted-password<encrypted_password>|-i3-clear-password<clear_password>}
-action communication-key-change
-type aes

Anchor
Distributingthenewencryptionsettingstoallservers Distributingthenewencryptionsettingstoallservers

Distributing the new encryption settings to all servers

For the new encryption settings to take effect, you must distribute them to all servers, completing no later than 24 hours after you changed the encryption configuration on the Precise FocalPoint server.

...

See Distributing the new encryption settings to all servers on page 216.

If the new encryption settings were successfully received on all servers, the scan results in an output like the following:

...

For general information regarding configuring HTTPS mode, see Apache Tomcat server instructions found at this site: http://tomcat.apache.org/tomcat-4.1-doc/ssl-howto.html

For information regarding configuring J2EE to work in HTTPS mode, see About Security Options in the Precise for J2EE User Guide.For information on installing your own certificate for J2EE, see the Creating and installing certificates for SSL on page of the Precise Administration Guide.

Changing the session timeout for an Apache Tomcat server

...

1. Before downloading and installing the SiteMinder Web agent, perform the steps described in the procedure, " To make changes on the System tab in the Configuring the SiteMinder Policy server.".
2. Download and install the latest SiteMinder Web agent for Apache Web servers.
   Verify that the version you download supports the Apache Web server version that we support – in this case, version 2.2.3 and that you download the file for the platform on which your Apache Web server is installed.
   
   1. Download the agent from https//support.netegrity.com.
   2. Insert your user name and password.
   3. Select Tools in the left pane.
   4. Choose Download Manager.
   5. Select SiteMinder Web Agent in the Download a product drop-down menu.
   6. Choose SiteMinder 6.x QMR's.
   7. Choose the agent to be downloaded.
3. After installing the SiteMinder Web agent, configure it according to the SiteMinder's Web agent Installation and Configuration guide.
4. Open the WebAgent.conf file in the \Program Files\Apache Software Foundation\Apache2.2\conf folder, and then set EnableWebAgent="YES".
5. Add the Apache Web server as a protected resource to the SiteMinder's protected resources.
6. Restart the machine after you have installed the Web Agent.

...

1. Log in to the Policy server management application.
2. Define the protection on the Precise application by performing steps on two of the three main tabs (System, Domains, Global Policies) on the main window of the Policy server management application as described in separate procedures.

...