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

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 IBM Lotus Domino 6.5.4

Chapter 5 Post-Installation Configuration: Policy Agent 2.2 for IBM Lotus Domino 6.5.4

This chapter describes configuration and other post-installation considerations and tasks regarding Policy Agent 2.2 for IBM Lotus Domino 6.5.4 on the supported platforms.

For all supported platforms, configuring the DSAPI filter is a required task. After you configure the DSAPI filter, follow the guidelines for verifying that the installation was successful. This chapter is divided into the following sections:

As the preceding list indicates, many post-installation configuration tasks vary by platform. Refer to the platform-specific section that pertains to your site's deployment to perform the applicable tasks as described. The following list summarizes how various tasks apply to the supported platforms:

Using a Lotus Domino database with Agent for IBM Lotus Domino 6.5.4: This task applies to all supported platforms, but is only required when you want the agent to check the Lotus Domino database for a user name after the agent has authenticated that user name.
Setting file ownership and permissions: This task is required on Solaris systems and Linux systems for the agent to function. This task does not apply to Windows systems.
Configuring the IBM Lotus Domino 6.5.4 DSAPI filter: This task is required on all supported platforms for the agent to function.
Configuring the agent for multiple instances of IBM Lotus Domino 6.5.4: This task applies to Solaris systems and Linux systems, but is only required when the agent is deployed on multiple instances of the IBM Lotus Domino 6.5.4 server.
Configuring SSL with the web agent: This task applies to all supported platforms, but is only required when you want to use SSL with Agent for IBM Lotus Domino 6.5.4.

After completing the applicable tasks described in this chapter and after verifying that the installation was successful, perform the applicable tasks to configure the web agent to your site's specific needs as explained in Chapter 6, Managing Policy Agent 2.2 for IBM Lotus Domino 6.5.4.

All Systems: Using the Lotus Domino Database with Agent for IBM Lotus Domino 6.5.4

You can configure Agent for IBM Lotus Domino 6.5.4 to check the Lotus Domino database for each user name after the agent authenticates the user name. This configuration involves editing one property in the web agent AMAgent.properties configuration file as explained in the task description that follows.

The following property controls this feature:

com.sun.am.policy.agents.config.domino.check_name_database

The default setting for this property is false. When this property is set to false, after authenticating a user name, the agent does not check the Lotus Domino database for that user name. When this property is set to true, after authenticating a user name, the agent checks the Lotus Domino database for that user name. The following task description, shows this property set to true.

To Configure Agent for IBM Lotus Domino 6.5.4 To Use the Lotus Domino Database

For this task you must edit the web agent AMAgent.properties configuration file.

Set the value of the following property to true as shown:

com.sun.am.policy.agents.config.domino.check_name_database = true

Solaris Systems: Configuring Agent for IBM Lotus Domino 6.5.4

This section provides task descriptions for the following procedures:

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 on Agent for IBM Lotus Domino 6.5.4

On Solaris systems, the IBM Lotus Domino 6.5.4 server must run as a non-root user. The default user created for this purpose during installation of the IBM Lotus Domino 6.5.4 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 6.5.4 user name of notes is used.

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

/etc/opt/SUNWam/agents/domino/config/_PathInstanceName/AMAgent.properties
/var/opt/SUNWam/agents/debug/_PathInstanceName/amAgent
PolicyAgent-base/SUNWam/agents/domino/lib/libamdomino6.so

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/cert-dir, ensure that /optcert-dir/{cert7.db,key3.db} has the necessary permissions by using the following command:

chown notes:notes /opt/cert-dir/cert7.db /opt/cert-dir/key3.db

Where cert-dir represents the directory in which certificates and key stores related to SSL are located.

Solaris Systems: Configuring the DSAPI Filter With Agent for IBM Lotus Domino 6.5.4

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 6.5.4 server. The task description that follows explains how to configure the DSAPI filter.

To Configure the DSAPI Filter With Agent for IBM Lotus Domino 6.5.4 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.

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 6.5.4 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/SUNWam/agents/domino/lib/libamdomino6.so
```

Click the Save and Close button to save the changes.

Open the IBM Lotus Domino 6.5.4 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 Agent for IBM Lotus Domino 6.5.4 on Multiple Web Server Instances

To configure Agent for IBM Lotus Domino 6.5.4 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 6.5.4 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

To Configure Agent for IBM Lotus Domino 6.5.4 on Multiple Web Server Instances on Solaris Systems

To configure the agent for additional IBM Lotus Domino 6.5.4 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 IBM Lotus Domino 6.5.4.

For information on each of the prompts, see Command-Line Installation of Agent for IBM Lotus Domino 6.5.4 on Solaris Systems.

In general, information needs to be entered for both the protected IBM Lotus Domino 6.5.4 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 Agent for IBM Lotus Domino 6.5.4

During installation, if you choose the HTTPS protocol, Agent for IBM Lotus Domino 6.5.4 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 6.5.4 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 IBM Lotus Domino 6.5.4 server.

To Configure Notification on Agent for IBM Lotus Domino 6.5.4 for SSL on Solaris Systems

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

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

Default Trust Behavior of Agent for IBM Lotus Domino 6.5.4 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 6.5.4 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 IBM Lotus Domino 6.5.4 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 IBM Lotus Domino 6.5.4 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/domino/cert

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 6.5.4 Instance on Solaris Systems

The root CA certificate that you install on the remote instance of IBM Lotus Domino 6.5.4 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 6.5.4 on Solaris Systems

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

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

Install the root CA certificate.

Remember that the root CA certificate that you install on the IBM Lotus Domino 6.5.4 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.

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

Restart the IBM Lotus Domino 6.5.4 server.

Windows Systems: Configuring Agent for IBM Lotus Domino 6.5.4

This section provides task descriptions for the following procedures:

As described in the following subsections, configure the DSAPI filter. Then, perform the procedure for verifying a successful installation. Next, determine if the remaining procedure described in this section applies to your site's deployment scenario and perform the procedure if necessary.

Windows Systems: Configuring the DSAPI Filter With Agent for IBM Lotus Domino 6.5.4

To Configure the DSAPI Filter With Agent for IBM Lotus Domino 6.5.4 on Windows Systems

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 6.5.4 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\\domino\\bin\\amdomino6.dll
```

Click the Save and Close button to save the changes.

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

Next Steps

Windows Systems: Using SSL With Agent for IBM Lotus Domino 6.5.4

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

To Configure Notification on Agent for IBM Lotus Domino 6.5.4 for SSL on Windows Systems

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

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

Default Trust Behavior of Agent for IBM Lotus Domino 6.5.4 on Windows Systems

This section only applies when Access Manager itself is running SSL. By default, Agent for IBM Lotus Domino 6.5.4 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 IBM Lotus Domino 6.5.4 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 IBM Lotus Domino 6.5.4 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 IBM Lotus Domino 6.5.4 on Windows Systems

The root CA certificate that you install on the IBM Lotus Domino 6.5.4 instance that the agent protects 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 6.5.4 on Windows Systems

(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 IBM Lotus Domino 6.5.4 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
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.

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:

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

Restart the IBM Lotus Domino 6.5.4 server.

Linux Systems: Configuring Agent for IBM Lotus Domino 6.5.4

This section provides task descriptions for the following:

Linux Systems: Setting File Ownership and Permissions on Agent for IBM Lotus Domino 6.5.4

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

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

/etc/opt/agents/domino6/config/_PathInstanceName/AMAgent.properties
/var/opt/agents/debug/_PathInstanceName/amAgent
PolicyAgent-base/agents/domino6/lib/libamdomino6.so

PolicyAgent-base

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

_PathInstanceName

/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/agents/domino6/config/_PathInstanceName
chown notes:notes /var/tmp/debug/_PathInstanceName/
chown notes:notes PolicyAgent-base/agents/domino6/lib/libamdomino6.so

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

chown notes:notes /opt/cert-dir/cert7.db /opt/cert-dir/key3.db

Where cert-dir represents the directory in which certificates and key stores related to SSL are located.

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

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

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 6.5.4 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 6.5.4 Quick Console and restart the server by entering the following commands:
tell http quit load http

Next Steps

Linux Systems: Configuring Agent for IBM Lotus Domino 6.5.4 on Multiple Web Server Instances

To configure Agent for IBM Lotus Domino 6.5.4 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 Agent for IBM Lotus Domino 6.5.4 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 Agent for IBM Lotus Domino 6.5.4 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 Agent for IBM Lotus Domino 6.5.4.

For information on each of the prompts, see GUI Installation of Agent for IBM Lotus Domino 6.5.4 on Linux Systems

In general, information needs to be entered for both the protected IBM Lotus Domino 6.5.4 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 Agent for IBM Lotus Domino 6.5.4

During installation, if you chose the HTTPS protocol, Agent for IBM Lotus Domino 6.5.4 is automatically configured and ready to communicate over SSL. Before proceeding with the following tasks in this section, ensure that IBM Lotus Domino 6.5.4 is configured for SSL.

Caution –

To Configure Notification on Agent for IBM Lotus Domino 6.5.4 for SSL on Linux Systems

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

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

Default Trust Behavior of Agent for IBM Lotus Domino 6.5.4 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 6.5.4 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 IBM Lotus Domino 6.5.4 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 IBM Lotus Domino 6.5.4 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 6.5.4 Instance on Linux Systems

The root CA certificate that you install on the remote instance of IBM Lotus Domino 6.5.4 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 6.5.4 on Linux Systems

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

All Systems: Verifying a Successful Installation on Policy Agent 2.2

After installing a web agent, ensure that the agent is installed successfully. Two methods are available for verifying a successful web agent installation. Perform both for best results.

To Verify a Successful Installation

Attempt to access a resource on the deployment container where the agent is installed.

If the web agent is installed correctly, accessing any resource should take you to the Access Manager login page. After a successful authentication, if the policy is properly defined, you should be able to view the resource.

Check the web agent AMAgent.properties configuration file.

Make sure that each property is set properly. For information on the properties in this file, see Appendix C, Web Agent AMAgent.properties Configuration File.