Sun Java System Access Manager Policy Agent 2.2 Guide for Sun Java System Web Server 6.1

Previous: Chapter 4 The Relationship Between the Agent Profile and Web Agents in Policy Agent 2.2
Next: Chapter 6 Managing Policy Agent 2.2 for Sun Java System Web Server 6.1

Chapter 5 Configuration of Multiple Agents or SSL Setup: Policy Agent 2.2 for Sun Java System Web Server 6.1

This chapter describes configuration and other post-installation considerations and tasks regarding Policy Agent 2.2 for Sun Java System Web Server 6.1 on the supported platforms as follows:

This chapter covers two configuration tasks of Policy Agent 2.2 for Sun Java System Web Server 6.1, specifically the configuration of the agent for multiple instances of Sun Java System Web Server 6.1 and the configuration of SSL with the agent. Perform these tasks if they apply to your site's deployment. After completing the applicable tasks described in this chapter, perform the tasks to configure the web agent to your site's specific needs as explained in Chapter 6, Managing Policy Agent 2.2 for Sun Java System Web Server 6.1.

Solaris Systems: Configuring Agent for Sun Java System Web Server 6.1

This section provides task descriptions for the following:

Only perform a task if a respective condition applies.

Solaris Systems: Configuring Agent for Sun Java System Web Server 6.1 on Multiple Web Server Instances

To configure Agent for Sun Java System Web Server 6.1 for multiple web server instances on a single computer, use the GUI or command-line version of the agent installation program to install the first agent. After the first agent is installed, you can then configure the agent for multiple instances of Sun Java System Web Server 6.1 using the config script that is copied into the system during the agent installation. This script must be run in the command line as described in the next section. The config script and the unconfig script are both located in the following directory:

PolicyAgent-base/SUNWam/agents/es6/bin

To Configure Agent for Sun Java System Web Server 6.1 on Multiple Web Server Instances on Solaris Systems

To configure the agent for additional Sun Java System Web Server 6.1 instances on a system, run the config script in the bin directory using the following command:

# ./config

Follow the prompts to install additional instances of Agent for Sun Java System Web Server 6.1.

For information on each of the prompts, see Command-Line Installation of Agent for Sun Java System Web Server 6.1 on Solaris Systems.

In general, information needs to be entered for both the protected Sun Java System Web Server 6.1 instance and the instances of Access Manager. The following text serves as an example.

# ./config
Enter the Web Server Instance Directory:
Enter the Local Hostname:
Enter the Agent Web Server Port: [80]
Select Agent Web Server Protocol: [1] http [2] https --> [1]
Enter the Agent Deployment URI [/amagent]
Enter the Access Manager Hostname:
Enter the Access Manager Port: [58080]
Select Access Manager Protocol: [1] http [2] https --> [1]
Enter the Access Manager Deployment URI [/amserver]
Enter the Access Manager's Console Deployment URI [/amconsole]
Do You Want Failover Server Support: [1] yes [2] No --> [2]
Enter the User Name [UrlAccessAgent]
Enter Agent-Access Manager shared secret:
Re-enter Agent-Access Manager shared secret:
Is CDSSO Enabled: [1] yes [2] no --> [2]
Configuring webserver ...
Done.

Note –

Be sure to use the unconfig script to uninstall any web agent that was installed using the config script. You cannot use the GUI installation program to uninstall web agents that were installed using the command line. The GUI uninstallation program must be executed only after unconfiguring all the existing web agents using the command-line unconfig script.

Solaris Systems: Using SSL With Agent for Sun Java System Web Server 6.1

During installation, if you choose the HTTPS protocol, Agent for Sun Java System Web Server 6.1 is automatically configured and ready to communicate over Secure Sockets Layer (SSL). Before proceeding with tasks in this section, ensure that the Sun Java System Web Server 6.1 instance is configured for SSL.

Caution –

You should have a solid understanding of SSL concepts and the security certificates required to enable communication over the HTTPS protocol. See the documentation for Sun Java System Web Server 6.1.

To Configure Notification on Agent for Sun Java System Web Server 6.1 for SSL on Solaris Systems

If Sun Java System Web Server 6.1 is running in SSL mode and is receiving notifications, first perform the following broadly defined steps:

Add the Sun Java System Web Server 6.1 certificate’s root CA certificate to the Access Manager’s certificate database.

Mark the CA root certificate as trusted to enable Access Manager to successfully send notifications to Agent for Sun Java System Web Server 6.1.

Default Trust Behavior of Agent for Sun Java System Web Server 6.1 on Solaris Systems

This section only applies when Access Manager itself is running SSL. By default, the web agent installed on a remote Sun Java System Web Server 6.1 instance trusts any server certificate presented over SSL by the Access Manager host. The web agent does not check the root Certificate Authority (CA) certificate. If the Access Manager host is SSL-enabled and you want the agent to perform certificate checking, adhere to the guidelines as described in the following subsections:

Disabling the Default Trust Behavior of Agent for Sun Java System Web Server 6.1 on Solaris Systems

The following property in the web agent AMAgent.properties configuration file controls the agent’s trust behavior, and by default it is set to true:

com.sun.am.trust_server_certs

With this property set to true, the web agent does not perform certificate checking. On Solaris systems, setting this property to false is one of the steps involved in enabling the web agent to perform certificate checking as illustrated in the following task.

To Disable the Default Trust Behavior of Agent for Sun Java System Web Server 6.1 on Solaris Systems

Set the following property in the web agent AMAgent.properties configuration file to false as follows:
```
com.sun.am.trust_server_certs = false
```

Set the directory Cert DB in the web agent AMAgent.properties configuration file as shown in the following example:

com.sun.am.sslcert.dir = /opt/SUNWam/servers/alias

Set the Cert DB Prefix, if required.

In cases where the specified Cert DB directory has multiple certificate databases, the following property must be set to the prefix of the certificate database to be used:

com.sun.am.certdb.prefix

Set the property as follows:
com.sun.am.certdb.prefix = https-host.domain.com.host-

Installing the Access Manager Root CA Certificate for a Remote Sun Java System Web Server 6.1 Instance on Solaris Systems

The root CA certificate that you install on the remote instance of Sun Java System Web Server 6.1 must be the same one that is installed on the Access Manager host.

To Install the Access Manager Root CA Certificate on Sun Java System Web Server 6.1 on Solaris Systems

For instructions on installing a root CA certificate, see the documentation for Sun Java System Web Server 6.1.

Windows Systems: Configuring Agent for Sun Java System Web Server 6.1

This section provides task descriptions for using SSL with Agent for Sun Java System Web Server 6.1.

Windows Systems: Using SSL With Agent for Sun Java System Web Server 6.1

During installation, if you choose the HTTPS protocol, Agent for Sun Java System Web Server 6.1 is automatically configured and ready to communicate over SSL. Before proceeding with the tasks in this section, ensure that the Sun Java System Web Server 6.1 instance is configured for SSL.

Caution –

You should have a solid understanding of SSL concepts and the security certificates required to enable communication over the HTTPS protocol. See the documentation for Sun Java System Web Server 6.1.

To Configure Notification on Agent for Sun Java System Web Server 6.1 for SSL on Windows Systems

If Sun Java System Web Server 6.1 is running in SSL mode and is receiving notifications, first perform the following broadly defined steps:

Add the Sun Java System Web Server 6.1 certificate’s root CA certificate to the Access Manager’s certificate database.

Mark the CA root certificate as trusted to enable Access Manager to successfully send notifications to Agent for Sun Java System Web Server 6.1.

Default Trust Behavior of Agent for Sun Java System Web Server 6.1 on Windows Systems

This section only applies when Access Manager itself is running SSL. By default, Agent for Sun Java System Web Server 6.1 trusts any server certificate presented over SSL by the Access Manager host. The web agent does not check the root Certificate Authority (CA) certificate. If the Access Manager host is SSL-enabled and you want the agent to perform certificate checking, adhere to the guidelines as described in the following subsections:

Disabling the Default Trust Behavior of Agent for Sun Java System Web Server 6.1 on Windows Systems

The following property exists in the web agent AMAgent.properties configuration file, and by default it is set to true:

com.sun.am.trust_server_certs

With this property set to true, the web agent does not perform certificate checking. On Windows systems, enabling the web agent to perform certificate checking is a one-step process that only involves setting this property to false as illustrated in the following task.

To Disable the Default Trust Behavior of Agent for Sun Java System Web Server 6.1 on Windows Systems

Set the following property in the web agent AMAgent.properties configuration file to false as follows:
```
com.sun.am.trust_server_certs = false
```

Installing the Access Manager Root CA Certificate on Sun Java System Web Server 6.1 on Windows Systems

The root CA certificate that you install on the Sun Java System Web Server 6.1 instance that the agent protects must be the same one that is installed on the Access Manager host.

To Install the Access Manager Root CA Certificate on Sun Java System Web Server 6.1 on Windows Systems

For instructions on installing a root CA certificate, see the documentation for Sun Java System Web Server 6.1.

Linux Systems: Configuring Agent for Sun Java System Web Server 6.1

This section provides task descriptions for the following:

Only perform a task if a respective condition applies.

Linux Systems: Configuring Agent for Sun Java System Web Server 6.1 on Multiple Web Server Instances

To configure Agent for Sun Java System Web Server 6.1 for multiple web server instances on a single Linux computer, use the GUI or the command-line version of the agent installation program to install the first agent. After the first agent is installed, you can then install successive agents using the config_es6_linux script. This script must be run using the command line as described in the next section. The config_es6_linux script and the unconfig_es6_linux script are both located in the following directory:

PolicyAgent-base/agents/es6/bin

To Configure Agent for Sun Java System Web Server 6.1 on Multiple Web Server Instances on Linux Systems

Perform the following steps if you want to configure additional agent instances on a system after the original instance of Agent for Sun Java System Web Server 6.1 has been installed.

Run the config_es6_linux script in the bin directory using the following command:
# ./config_es6_linux

Follow the prompts to install additional instances of Agent for Sun Java System Web Server 6.1.

For information on each of the prompts, see GUI Installation of Agent for Sun Java System Web Server 6.1 on Linux Systems

In general, information needs to be entered for both the protected Sun Java System Web Server 6.1 instance and the instances of Access Manager. The following text serves as an example:

# ./config_es6_linux
Enter the Web Server Instance Directory:
Enter the Local Hostname:
Enter the Agent Web Server Port: [80]
Select Agent Web Server Protocol: [1] http [2] https --> [1]
Enter the Agent Deployment URI [/amagent]
Enter the Access Manager Hostname:
Enter the Access Manager Port: [58080]
Select Access Manager Protocol: [1] http [2] https --> [1]
Enter the Access Manager Deployment URI [/amserver]
Enter the Access Manager's Console Deployment URI [/amconsole]
Do You Want Failover Server Support: [1] yes [2] No --> [2]
Enter the User Name [UrlAccessAgent]
Enter Agent-Access Manager shared secret:
Re-enter Agent-Access Manager shared secret:
Is CDSSO Enabled: [1] yes [2] no --> [2]
Configuring webserver ...
Done.

Note –

Be sure to use the unconfig_es6_linux script to uninstall any agent that was installed using the config_es6_linux script. You cannot use the GUI installation program to uninstall agents that were installed using the command line. The GUI uninstallation program must be executed only after unconfiguring all the existing agents installed using command-line unconfig_es6_linux script.

Linux Systems: Using SSL With Agent for Sun Java System Web Server 6.1

During installation, if you chose the HTTPS protocol, Agent for Sun Java System Web Server 6.1 is automatically configured and ready to communicate over SSL. Before proceeding with the following tasks in this section, ensure that Sun Java System Web Server 6.1 is configured for SSL.

Caution –

You should have a solid understanding of SSL concepts and the security certificates required to enable communication over the HTTPS protocol. See the documentation for Sun Java System Web Server 6.1.

To Configure Notification on Agent for Sun Java System Web Server 6.1 for SSL on Linux Systems

If Sun Java System Web Server 6.1 is running in SSL mode and is receiving notifications, first perform the following broadly defined steps:

Add the Sun Java System Web Server 6.1 certificate’s root CA certificate to the Access Manager’s certificate database.

Mark the CA root certificate as trusted to enable Access Manager to successfully send notifications to Agent for Sun Java System Web Server 6.1.

Default Trust Behavior of Agent for Sun Java System Web Server 6.1 on Linux Systems

This section only applies when Access Manager itself is running SSL. By default, the agent installed on a remote Sun Java System Web Server 6.1 instance will trust any server certificate presented over SSL by the Access Manager host. The web agent does not check the root Certificate Authority (CA) certificate. If the Access Manager host is SSL-enabled and you want the agent to perform certificate checking, adhere to the guidelines as described in the following subsections:

Disabling the Default Trust Behavior of Agent for Sun Java System Web Server 6.1 on Linux Systems

The following property in the web agent AMAgent.properties configuration file controls the agent’s trust behavior, which by default it is set to true:

com.sun.am.trust_server_certs

With this property set to true, the web agent does not perform certificate checking. On Linux systems, enabling the web agent to perform certificate checking is a one-step process that only involves setting this property to false as illustrated in the following task.

To Disable the Default Trust Behavior of Agent for Sun Java System Web Server 6.1 on Linux Systems

Set the following property in the web agent AMAgent.properties configuration file to false as follows:
```
com.sun.am.trust_server_certs = false
```

Installing the Access Manager Root CA Certificate for a Remote Sun Java System Web Server 6.1 Instance on Linux Systems

The root CA certificate that you install on the remote instance of Sun Java System Web Server 6.1 must be the same one that is installed on the Access Manager host.

To Install the Access Manager Root CA Certificate on Sun Java System Web Server 6.1 on Linux Systems

For instructions on installing a root CA certificate, see the documentation for Sun Java System Web Server 6.1.