test

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

Solaris Systems: Configuring the IBM Lotus Domino 7.0 Agent

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.

Solaris Systems: Setting File Ownership and Permissions for the IBM Lotus Domino 7.0 Agent

On Solaris systems, the IBM Lotus Domino 7.0 server must run as a non-root user. The default user created for this purpose during installation of the IBM Lotus Domino 7.0 server is notes. However, the actual user name will be different if this default was not accepted. For example purposes in this section, the default IBM Lotus Domino 7.0 user name of notes is used.

To enable the IBM Lotus Domino 7.0 agent to work properly, ensure that the notes user has read permissions to the following files:

PolicyAgent-base

represents the directory you choose in which to install the web agent

_PathInstanceName

represents a directory that is created and named during agent installation. This name is derived from the path to the Lotus Domino Data directory where slashes are converted to underscores. For this example, the path to the Lotus Domino Data directory is as follows:

/local/notesdata

Based on the preceding path, during installation, the following _PathInstanceName directory would be created:

_local_notesdata

You can set the required permissions to the files by issuing the following commands:

chown notes:notes /etc/opt/SUNWam/agents/domino/config/_PathInstanceName
chown notes:notes /var/opt/SUNWam/agents/debug/_PathInstanceName/
chown notes:notes PolicyAgent-base/SUNWam/agents/domino/lib/libamdomino6.so

Additionally, if Access Manager is running in SSL mode, the files cert7.db and key3.db must also allow read access to the notes user. These files are available in the directory specified by the property com.sun.am.sslcert.dir in the web agent AMAgent.properties configuration file.

For example, if the property is set as com.sun.am.sslcert.dir = /opt/my-agents-dir, ensure that /opt/my-agents-dir/{cert7.db,key3.db} has the necessary permissions by using the following command:

chown notes:notes /opt/my-agents-dir/cert7.db /opt/my-agents-dir/key3.db

Solaris 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.

ProcedureTo Configure the DSAPI Filter for the IBM Lotus Domino 7.0 Agent on Solaris 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.

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

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

    A window appears, presenting a list of servers.

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

  4. Click Internet Protocols.

  5. Select the HTTP tab.

  6. In the DSAPI Filter File Names field, enter the following file name:

    PolicyAgent-base/SUNWam/agents/domino/lib/libamdomino6.so

  7. Click the Save and Close button to save the changes.

  8. 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.

Solaris 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 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 IBM Lotus Domino 7.0 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/domino/bin

ProcedureTo Configure the IBM Lotus Domino 7.0 Agent on Multiple Web Server Instances on Solaris Systems

  1. To configure the agent for additional IBM Lotus Domino 7.0 instances on a system, run the config script in the bin directory using the following command:

    # ./config

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

    For information on each of the prompts, see Installing the IBM Lotus Domino 7.0 Agent Using the Command-Line Interface (CLI) 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 example.


    # ./config
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 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 the IBM Lotus Domino 7.0 Agent

During installation, if you choose the HTTPS protocol, the IBM Lotus Domino 7.0 agent is automatically configured and ready to communicate over Secure Sockets Layer (SSL). Before proceeding with tasks in this section, ensure that the IBM Lotus Domino 7.0 instance is configured for SSL.

Caution – 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 IBM Lotus Domino 7.0 server.

ProcedureTo Configure Notifications for the IBM Lotus Domino 7.0 Agent for SSL on Solaris Systems

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

  1. Add the IBM Lotus Domino 7.0 certificate’s root CA certificate to the Access Manager’s certificate database.

  2. 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 Solaris Systems

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

ProcedureTo Disable the Default Trust Behavior of the IBM Lotus Domino 7.0 Agent on Solaris Systems

  1. Set the following property in the web agent AMAgent.properties configuration file to false as follows:

    com.sun.am.trust_server_certs = false

  2. 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/domino/cert

  3. 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 IBM Lotus Domino 7.0 Instance on Solaris 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.

ProcedureTo Install the Access Manager Root CA Certificate on IBM Lotus Domino 7.0 on Solaris Systems

The following steps outline a method for installing Access Manager Root CA Certificate on the IBM Lotus Domino 7.0 server. However, see the documentation for the IBM Lotus Domino 7.0 server for more information about installing certificates.

  1. (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/SUNWam/agents/domino/cert/certutil -N -d .

  2. Install the root CA certificate.

    Remember that the root CA certificate that you install on the IBM Lotus Domino 7.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/SUNWam/agents/domino/cert/certutil -A -n cert-name -t
"C,C,C" -d cert-dir -i cert-file
    cert-name

    The name for this root CA certificate.

    cert-dir

    The directory where the certificate and key stores are located.

    cert-file

    The base-64 encoded root CA certificate file.

    For more information on the cetrutil utility enter cetrutil -H for Help.

  3. To verify that the certificate is properly installed, in the command line, issue the following command:


    PolicyAgent-base/SUNWam/agents/domino/cert/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:


    Certificate Name                             Trust Attrubutes


      cert-name                                      C,C,C

p    Valid peer
P    Trusted peer (implies c)
c    Valid CA
T    Trusted CA to issue client certs (implies c)
C    Trusted CA to certs(only server certs for ssl) (implies c)
u    User cert
w    Send warning

  4. Restart the IBM Lotus Domino 7.0 server.