3 Testing the Connector

After you deploy the connector, you must test it to ensure that it functions as expected.

Note:

In earlier releases of this guide, the connector was referred to as the integration.

This chapter contains the following sections:

• Running Connector Tests

• Troubleshooting

Running Connector Tests

This section discusses test cases that you can perform by using the troubleshooting utility.

You can use the troubleshooting utility to directly use the connector to identify the cause of problems associated with connecting to the target system server and performing basic operations on the target system.

Before you can use the troubleshooting utility, you must set the required values in the config.properties file. This file is in the xellerate_home/xellerate/XLIntegrations/ClearTrust/tests/config/config.properties directory.

After you specify the required values in the config.properties file, perform the following steps to run the test cases:

1. Modify the classpath file to include the following:

   xellerate_home/Xellerate/XLIntegrations/ClearTrust/lib/xliClearTrust.jar
   xellerate_home/Xellerate/XLIntegrations/ClearTrust/tests/lib/xliClearTrustTest.jar
   xellerate_home/Xellerate/ext/ct_admin_api.jar
   xellerate_home/Xellerate/ext/ct_runtime_api.jar
   xellerate_home/Xellerate/ext/log4j-1.2.8.jar
   xellerate_home/Xellerate/lib/xl.jar
   xellerate_home/Xellerate/XLIntegrations/ClearTrust/tests
   
   

2. Use the following table to modify the default attributes of the config.properties file. This file is in the xellerate_home/Xellerate/XLIntegrations/ClearTrust/tests/config directory.

   Attribute Name	Description	Default Value
   machinename	The name or IP address of the computer on which the RSA ClearTrust Entitlements server is running	192.168.50.50
   port	The number of the port on which the RSA ClearTrust Entitlements server is listening	5601
   sslmode	The Secure Sockets Layer (SSL) mode that the Entitlements server is using (CLEAR, SSL_ANON, or SSL_AUTH)	CLEAR
   timeout	The timeout interval (in milliseconds) for connecting to the RSA ClearTrust Entitlements server	10000 ms
   admingroup	The name of the default RSA ClearTrust Administrative group	Default Administrative Group
   adminrole	The name of the default RSA ClearTrust Administrative role	Default Administrative Role
   action	The action that is to be tested when Oracle Identity Manager connects to RSA ClearTrust The action can be connect, createuser, modifyattributes, getattributes, or deleteuser.	createuser
   userid	The User ID Ensure that the ID does not exist in the RSA ClearTrust database.	c4
   password	The user's password	welcome1
   firstname	The user's first name	Jane
   lastname	The user's last name	Doe
   email	The user's e-mail address	[e-mail]
   startdate	The user's date of hire All dates should be in the following format: YYYY-MM-DD	2004-02-28
   enddate	The user's account termination date	2005-02-28
   password expirationdate	The date on which the user's password expires	2005-02-28
   islock	This Boolean attribute represents whether or not the user is locked in RSA ClearTrust If the action attribute is set to connect, then this attribute does not apply.	false
   loggerfile	The location and name of the log file	logs/Test_CTConnect.log
   loggerlevel	The level of logging that is required The level of logging can be DEBUG, INFO, WARN, or FATAL.	DEBUG

   
   

3. Enter a command similar to the following to run the CTConnectTest java class:

   java CTConnectTest config.properties ctadmin ctpassword
   
   

   For example:

   java com.thortech.xl.integration.ct.tests.CTConnectTest 
   config/config.properties admin admin
   
   

4. To verify that the designated action (for example, creating a user in RSA ClearTrust) is successful, check the log file specified in the config.properties file.

   The following is the sample output displayed in the log file:

   29 Mar 2004 15:32:19 INFO Constructor: logs/Test_CTConnect.log DEBUG 
   29 Mar 2004 15:33:08 INFO Constructor: logs/Test_CTConnect.log DEBUG 
   29 Mar 2004 15:33:32 INFO Constructor: logs/Test_CTConnect.log DEBUG 
   29 Mar 2004 15:33:32 INFO CT_CONNECTION_SUCCESS 
   29 Mar 2004 15:36:46 INFO Constructor: logs/Test_CTConnect.log DEBUG 
   29 Mar 2004 15:36:46 INFO CT_CONNECTION_SUCCESS 
   29 Mar 2004 15:36:46 INFO CT_USERCREATION_SUCCESS 
   29 Mar 2004 15:36:46 INFO CT_CLOSECONNECTION_SUCCESS
   

Troubleshooting

The following table lists solutions to some commonly encountered issues associated with the connector.

Problem	Solution
Oracle Identity Manager cannot establish a connection with RSA ClearTrust.	Ensure that the RSA ClearTrust Entitlements server is running. Check the port on which the RSA ClearTrust Entitlements server is running. Verify that the same port number is specified in the Port parameter. Validate the administrator's user ID, password, group, and role by using the Oracle Identity Manager Administrative and User Console. Verify that the SSL mode in which the Entitlements server is running is the same as the SSL mode that is specified in the SSLMode parameter of the RSA ClearTrust IT Resource. Check that all required RSA ClearTrust JAR files are present in the xellerate_home/Xellerate/ext directory. Verify that the jnet.jar, jsse.jar, jcert.jar, and jce1_4.jar files are present in the xellerate_home/java/jre/lib/ext directory.
Oracle Identity Manager cannot modify a user's distinguished name.	The distinguished name must be unique in RSA ClearTrust. Verify that no other user has the same distinguished name.
Related classes for RSA ClearTrust are not found.	Ensure that the RSA ClearTrust JAR files are added into the classpath file correctly.
An incompatible version is found for some classes.	Ensure that Oracle Identity Manager is using JDK 1.4.2, and not JDK 1.3.
Oracle Identity Manager cannot provision a user with RSA ClearTrust. In addition, the following error message is displayed: Data validation failed.	Ensure that the AutoSave feature of the RSA ClearTrust provisioning process is enabled. Verify that the CTPrepopServerInfo adapter is compiled and assigned to the custom process form. Check the run-time and return variables of the connector to ensure that they are mapped properly.
Oracle Identity Manager cannot assign a default group to the user who has been provisioned with RSA ClearTrust. In addition, the following error message is displayed: CT_USERGROUP_OBJECTNOTFOUND_FAIL	Ensure that the default group specified in the RSA ClearTrust IT Resource matches the group created in RSA ClearTrust.