Oracle® Identity Manager Connector Guide for RSA ClearTrust Release 9.0.2 Part Number B32169-01 |
|
|
View PDF |
After you deploy the connector, you must test it to ensure that it functions as expected. This chapter discusses the following topics related to connector testing:
You can use the troubleshooting utility to identify the cause of problems associated with connecting to the target system and performing basic operations on the target system.
To use the troubleshooting utility:
Modify the CLASSPATH environment variable to include the following:
OIM_home\Xellerate\XLIntegrations\ClearTrust\lib\xliClearTrust.jar OIM_home\Xellerate\XLIntegrations\ClearTrust\tests\lib\xliClearTrustTest.jar OIM_home\Xellerate\ext\ct_admin_api.jar OIM_home\Xellerate\ext\ct_runtime_api.jar OIM_home\Xellerate\ext\log4j-1.2.8.jar OIM_home\Xellerate\lib\xl.jar OIM_home\Xellerate\XLIntegrations\ClearTrust\tests
Use the information in the following table to modify the default attributes given in the config.properties
file. This file is in the OIM_home
\xellerate\XLIntegrations\ClearTrust\tests\config\config.properties
directory.
Attribute Name | Description | Default Value |
---|---|---|
machinename |
Host name or IP address of the computer on which the RSA ClearTrust Entitlements Server is running | 192.168.50.50 |
port |
Port at which the RSA ClearTrust Entitlements Server is listening | 5601 |
sslmode |
Secure Sockets Layer (SSL) mode that the Entitlements Server is using: CLEAR , SSL_ANON , or SSL_AUTH |
CLEAR |
timeout |
Timeout interval (in milliseconds) for connecting to the RSA ClearTrust Entitlements Server | 10000 ms |
admingroup |
Name of the default RSA ClearTrust Administrative group | Default Administrative Group |
adminrole |
Name of the default RSA ClearTrust Administrative role | Default Administrative Role |
action |
Action that is to be tested when Oracle Identity Manager connects to RSA ClearTrust
The action can be |
createuser |
userid |
User ID
You must ensure that the ID does not exist in the RSA ClearTrust database. |
c4 |
password |
User's password | welcome1 |
firstname |
User's first name | Jane |
lastname |
User's last name | Doe |
email |
User's e-mail address | jane.doe@acmewidgets.com |
startdate |
User's date of hire
All dates should be in the following format:
|
2004-02-28 |
enddate |
User's account termination date | 2005-02-28 |
password expirationdate | Date on which the user's password expires | 2005-02-28 |
islock |
Specifies whether or not the user is locked in RSA ClearTrust
If the action attribute is set to |
false |
loggerfile |
Name and location of the log file | logs/Test_CTConnect.log |
loggerlevel |
Level of logging that is required
The level can be |
DEBUG |
Enter a command similar to the following to run the CTConnectTest
Java class file:
java CTConnectTest config.properties ctadmin ctpassword
For example:
java com.thortech.xl.integration.ct.tests.CTConnectTest config/config.properties admin admin
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 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
The following table lists solutions to some commonly encountered errors associated with the connector.