Archive Integration Guide › ICAP Agent › Integration Procedure for ICAP Clients › Configure the Proxy Server and ICAP Client

Configure the Proxy Server and ICAP Client

The proxy server must have an ICAP client installed. ICAP clients can process both requests and responses. See the documentation for your proxy server and ICAP client for full configuration details. For integration with CA DataMinder, you must:

1. Verify that a supported authentication method is enabled on the proxy server.

   If authentication is not enabled, the user identity cannot be passed from the ICAP client to the ICAP agent.

   If you are using a Blue Coat ProxySG server, see your Blue Coat documentation for details about configuring the LDAP, IWA, Windows SSO or Policy Substitution authentication methods.

2. Specify the port number assigned to the ICAP agent.

   This port must match the port specified by the AgentPort registry value. By default, this is 1344.

3. Identify the ICAP agent host machine. This allows the ICAP client to route requests and responses to the ICAP agent.

   For example, for Blue Coat ProxySG servers you must provide a service URL, formatted as shown below:

   icap://<ipaddress>:<port>/<reqmod>|<respmod>
   

   where:

   <ipaddress> is the IP address of the ICAP agent host machine.

   <port> specifies the port number used for communication between the ICAP client and ICAP agent. If you use the default port (1344), you can omit the port number from the URL.

   <reqmod>|<respmod> identifies the type of event, an HTTP request or HTTP response.

4. Enable the ICAP v1 options Client Address and Authenticated User.
5. Disable Preview Size for HTTP responses.

   This option is not supported by the CA DataMinder ICAP agent. If it is enabled, the ICAP agent may not work correctly.