Sun Java System Access Manager Policy Agent 2.2 Guide for IBM Lotus Domino 7.0

Linux Systems: Configuring the IBM Lotus Domino 7.0 Agent

This section provides task descriptions for the following:

After you check the file ownership and permissions (and reset if necessary), configure the DSAPI filter. Then, perform the procedure for verifying a successful installation. Next, determine if the remaining procedures described in this section apply to your site's deployment scenario. Perform the applicable procedures.

Linux Systems: Configuring the DSAPI Filter for the IBM Lotus Domino 7.0 Agent

Configuring the DSAPI filter is a required task. When the DSAPI filter is not configured properly, users are unable to access resources. The DSAPI filter authenticates users and passes their information to the IBM Lotus Domino 7.0 server. The task description that follows explains how to configure the DSAPI filter.

To Configure the DSAPI Filter for the IBM Lotus Domino 7.0 Agent on Linux Systems

If you want to configure the DSAPI filter for multiple server instances, repeat this task for each server instance that you want to support. Note that when multiple server instances exist, they all share a single web agent AMAgent.properties configuration file.

In the Lotus Domino Administrator web console, select the Configuration tab.

In the left pane, under Server, click All Server Documents

A window appears, presenting a list of servers.

From the listed servers, select the IBM Lotus Domino 7.0 server instance that you want to configure.

Click Internet Protocols.

Select the HTTP tab.

In the DSAPI Filter File Names field, enter the following file name:
```
PolicyAgent-base/agents/domino6/lib/libamdomino6.so
```

Click the Save and Close button to save the changes.

Open the IBM Lotus Domino 7.0 Quick Console and restart the server by entering the following commands:
tell http quit load http

Next Steps

After you have configured the DSAPI filter, verify that the installation was successful. For information about the verification process, see All Systems: Verifying a Successful Installation on Policy Agent 2.2.

Linux Systems: Configuring the IBM Lotus Domino 7.0 Agent on Multiple Web Server Instances

To configure the IBM Lotus Domino 7.0 agent 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_linux script. This script must be run in the command line as described in the next section. The config_linux script and the unconfig_linux script are both located in the following directory:

PolicyAgent-base/agents/domino6/bin

To Configure the IBM Lotus Domino 7.0 Agent on Multiple Web Server Instances on Linux Systems

Perform the following steps if you want to configure additional agents on a system after the original IBM Lotus Domino 7.0 agent has been installed.

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

Follow the prompts to install additional instances of the IBM Lotus Domino 7.0 agent.

For information about each of the prompts, see Installing the IBM Lotus Domino 7.0 Agent on UNIX and Linux Systems

In general, information needs to be entered for both the protected IBM Lotus Domino 7.0 instance and the instances of Access Manager. The following text serves as an example run:

# ./config_linux
Enter the Lotus Domino Data 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_linux script to uninstall any agent that was installed using the config_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_linux script.

Linux Systems: Using SSL With the IBM Lotus Domino 7.0 Agent

During installation, if you chose the HTTPS protocol, the IBM Lotus Domino 7.0 agent is automatically configured and ready to communicate over SSL. Before proceeding with the following tasks in this section, ensure that IBM Lotus Domino 7.0 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 the IBM Lotus Domino 7.0 server.

To Configure Notifications for the IBM Lotus Domino 7.0 Agent for SSL on Linux Systems

If IBM Lotus Domino 7.0 is running in SSL mode and is receiving notifications, first perform the following broadly defined steps:

Add the IBM Lotus Domino 7.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 IBM Lotus Domino 7.0 agent.

Default Trust Behavior of the IBM Lotus Domino 7.0 Agent on Linux Systems

This section only applies when Access Manager itself is running SSL. By default, the agent installed on a remote IBM Lotus Domino 7.0 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 the IBM Lotus Domino 7.0 Agent 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 the IBM Lotus Domino 7.0 Agent 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 IBM Lotus Domino 7.0 Instance on Linux Systems

The root CA certificate that you install on the remote instance of IBM Lotus Domino 7.0 must be the same certificate that is installed on the Access Manager host.

To Install the Access Manager Root CA Certificate on IBM Lotus Domino 7.0 on Linux Systems

For instructions on installing a root CA certificate on Linux systems, see the documentation for the IBM Lotus Domino 7.0 server.