The tasks described in this chapter are not required for this web agent to work, but might be desired. This chapter describes the following broadly-defined tasks:
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 Microsoft IIS 5.0.
Perform the tasks described in this chapter if you want to configure SSL with Agent for Microsoft IIS 5.0.
During installation, if you choose the HTTPS protocol, the agent for Microsoft IIS 5.0 is automatically configured and ready to communicate over SSL. Before proceeding with the tasks in this section, ensure that the Microsoft IIS 5.0 instance is configured for SSL.
You should have a solid understanding of SSL concepts and the security certificates required to enable communication over the HTTPS protocol. See the documentation that comes with Microsoft IIS 5.0.
Add the Microsoft IIS 5.0 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 the agent for Microsoft IIS 5.0.
This section only applies when Access Manager itself is running SSL. By default, Agent for Microsoft IIS 5.0 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:
The following property exists in the web agent AMAgent.properties configuration file, and by default it is set to true:
With this property set to true, the web agent does not perform certificate checking. 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.
Set the following property in the web agent AMAgent.properties configuration file to false as follows:
com.sun.am.trust_server_certs = false
The root CA certificate that you install on the Microsoft IIS 5.0 instance that the agent protects must be the same one that is installed on the Access Manager host.
(Conditional) If the certificate database has not yet been created, create it at a unique location using a command such as the following:
PolicyAgent-base\bin\certutil -N -d .
Install the root CA certificate.
Remember that the root CA certificate that you install on the Microsoft IIS 5.0 server must be the same certificate that is installed on the Access Manager host.
The following example demonstrates a command you can issue that uses the certutil utility to install the certificate:
PolicyAgent-base\bin\certutil -A -n cert-name -t "C,C,C" -d cert-dir -i cert-file
represents the name of this root CA certificate
represents the directory where the certificate and key stores are located.
represents the base-64 encoded root CA certificate file.
For more information on the certutil utility, see the online help by issuing the following command:
To verify that the certificate is properly installed, in the command line, issue the following command:
PolicyAgent-base\bin\certutil -L -d cert-dir
The root CA certificate is then listed in the output of the certutil -L command as illustrated in the following code example:
Restart the Microsoft IIS 5.0 server.
As explained in Preventing an Additional Authentication Prompt: Preparing to Install Agent for Microsoft IIS 5.0, preventing users from being prompted a second time for user name and password requires you to set the Basic Authentication filter. This section provides the final instructions of that process. At this point you have completed the tasks described in Preventing an Additional Authentication Prompt: Preparing to Install Agent for Microsoft IIS 5.0, installed the agent, and verified the installation. Furthermore, at this point, the authentication type is set to anonymous, which is the default setting. In the task that follows, you will change the authentication type to basic.
The following information is helpful for this task.
The default location of the web agent AMAgent.properties configuration file is as follows:
where PolicyAgent-base is the directory you choose in which to install the web agent. The default location of PolicyAgent-base is as follows:
Configure the com.sun.am.replaypasswd.key property in the AMAgent.properties configuration file as described in the substeps that follow.
This step is similar to a step described in To Deploy the Post Authentication Module in Access Manager where you are instructed to configure the com.sun.am.replaypasswd.key property in the Access Manager AMConfig.properties configuration file. The value used in that task, must also be used in this task.
Open the AMAgent.properties configuration file.
Add the following property to the file:
Add the appropriate string as the value of the com.sun.am.replaypasswd.key property.
For example, if the string used previously for the this same property, but in the Access Manager AMConfig.properties configuration file, was wuqUJyr=5Gc=, then this property would be set the same way as follows:
com.sun.am.replaypasswd.key = wuqUJyr=5Gc=
Set the authentication type of this agent by adding the following property and value to the AMAgent.properties configuration file:
com.sun.am.policy.agents.config.iis.auth_type = Basic
Enable basic authentication for this agent by adding the following property and value to the AMAgent.properties configuration file:
com.sun.am.policy.agents.config.iis.Use_Basic_Auth = true
Save and close the AMAgent.properties configuration file.
Restart the Microsoft IIS 5.0 server.