Oracle® Identity Manager Connector Guide for RSA ClearTrust Release 9.0.1 Part Number B31133-01 |
|
|
View PDF |
Deploying the connector involves the following steps:
The following table lists the installation requirements for the connector.
Item | Requirement |
---|---|
Oracle Identity Manager | Oracle Identity Manager release 8.5.3 or later |
Target system | RSA ClearTrust 5.5 or 5.52 |
Target system host platform | Any one of the following operating systems:
|
External code | The following files from the directory in which RSA ClearTrust is installed:
Refer to the "Step 3: Copying the Connector Files and External Code" section for information about copying these files to the required directories. |
This section discusses the following:
In the xellerate_home
/config/log.properties
file, add an entry similar to the following for a new log module:
log4j.logger.ADAPTERS.CTINTEGRATION=log_level
The following are the log levels that you can use:
DEBUG
INFO
WARN
ERROR
FATAL
The following table lists the files to be copied and the locations where you must copy them.
File in the Installation Media Directory | Destination Directory |
---|---|
The following files from the Web Access Control\RSA ClearTrust\RSA ClearTrust Rev 3.0.0\xml directory:
|
xellerate_home/xellerate/XLIntegrations/
|
The following files from the ClearTrust_installation_dir /lib directory:
|
xellerate_home/ThirdParty
|
ClearTrust_installation_dir/lib/xliClearTrust.jar
|
xellerate_home/xellerate/JavaTasks xellerate_home/xellerate/ScheduleTask |
The following files from the Web Access Control\RSA ClearTrust\RSA ClearTrust Rev 3.0.0\test directory:
config\config.properties lib\xlicleartrusttest.jar |
xellerate_home/xellerate/test
|
docs\B31133_01.pdf docs\html |
xellerate_home/xellerate/docs
|
You must import the following connector XML files into Oracle Identity Manager in the following sequence:
XLIClearTrust_DM.xml
XLIClearTrustEntityAdp_DM.xml
XLICTAutoSaveAdapter_DM.xml
XLIClearTrustScheduleTask_DM.xml
Caution:
If you do not import the connector XML files in the specified order, then the connector may not work.To import the connector XML file into Oracle Identity Manager:
Open the Oracle Identity Manager Administrative and User Console.
Click the Deployment Management link on the left navigation bar.
Click the Import link under Deployment Management. A dialog box for locating files is displayed.
Locate and open the XLIClearTrust_DM.xml
file, which is in the xellerate_home
/xellerate/XLIntegrations/ClearTrust/xml
directory. Details of this XML file are shown on the File Preview page.
Click Add File. The Substitutions page is displayed.
Click Next. The Confirmation page is displayed.
Click Next. The Provide IT Resource Instance Data page for the ClearTrust
IT resource is displayed.
Specify values for the parameters of the ClearTrust
IT resource. Refer to the table in the "Defining IT Resources" section for information about the values to be specified.
Click Next. The Provide IT Resource Instance Data page for a new instance of the ClearTrust
IT resource type is displayed.
Click Skip to specify that you do not want to define another IT resource. The Confirmation page is displayed.
See Also:
If you want to define another IT resource, then refer to Oracle Identity Manager Tools Reference Guide for instructions.Click View Selections.
The contents of the XML file are displayed on the Import page. You may see a cross-shaped icon along with some nodes. You must remove these nodes. To do this, right-click each such node and then select Remove.
Click Import. The connector XML file is imported into Oracle Identity Manager.
Perform the same procedure to import the remaining connector XML files. These files are in the xellerate_home
/xellerate/XLIntegrations/ClearTrust/xml
directory.
You must specify values for the ClearTrust
IT resource parameters listed in the following table.
Parameter Name | Parameter Description |
---|---|
CTAdminUserId |
Name of the RSA ClearTrust administrator
This is a required parameter. |
CTAdminPassword |
Password of the RSA ClearTrust administrator
This is a required parameter. |
MachineName or IPAddress |
Name or IP address of the computer on which the RSA ClearTrust entitlement server is running. This is the same computer to which Oracle Identity Manager connects.
This is a required parameter. |
Port |
Port number on which the RSA ClearTrust entitlement server is running
This is a required parameter. |
SSLMode |
SSL mode that is used to connect to the RSA ClearTrust server
Note: Ensure that RSA ClearTrust is running in this mode. Otherwise, Oracle Identity Manager cannot connect to RSA ClearTrust. This is a required parameter. |
TimeOut |
Timeout value for the connection that is established between Oracle Identity Manager and RSA ClearTrust
This is a required parameter. |
Default User Group |
Default user group in RSA ClearTrust
This is a required parameter. |
CaFileLocation |
Location of the CA certificate
This parameter is used only with mutual authentication. |
CaPassword |
Password for the CA certificate
This parameter is used only with mutual authentication. |
KsFileLocation |
Location of the keystore file
This parameter is used only with mutual authentication. |
KsPassword |
Password of the keystore file
This parameter is used only with mutual authentication. |
KeyAlias |
Key name that is to be used with the keystore file
This parameter is used only with mutual authentication. |
PrivatePassword |
Password for the private key in the keystore file
This parameter is used only with mutual authentication. |
TimeStamp |
This parameter is reserved for future use. |
CTAdmin Group |
Group to which the RSA ClearTrust administrative user belongs |
CTAdmin Role |
Role of the RSA ClearTrust administrative user |
After you specify values for these IT resource parameters, go to Step 9 of the procedure to import connector XML files.
This section discusses the following topics:
This section describes the following steps involved in configuring the Oracle Identity Manager server:
Open the Oracle Identity Manager Design Console.
Navigate to the System Configuration page.
Add a new entry in the Server category:
Name: Default date format
Keyword: XL.DefaultDateFormat
Value: MMM dd, yyyy 'at' hh:mm:ss z
Click Save.
This procedure involves the following steps:
Open the Resource Object form, and search for the Xellerate User. On the Object Reconciliation tab, add the required reconciliation fields. You must add the reconciliation fields that would be needed to provide input for mandatory fields in the Xellerate User form. For example, fields like User Login and First Name. Although the Password field is mandatory, you can ignore it. There must be mappings to all mandatory fields of the User Defined process form.
Open the Process Definition form, and search for the Xellerate User. On the Reconciliation Field Mappings tab, add the required reconciliation field mappings. All the mandatory fields of the user defined process form should be mapped.
Open the Reconciliation Rules form, and create a new rule for the Xellerate User resource object, with a rule element.
After creating the rule, select the Active check box.
Configuring reconciliation involves creating scheduled tasks for lookup fields and user reconciliations. To create a scheduled task:
Open the Oracle Identity Manager Design Console.
Expand the Xellerate Administration folder.
Select Task Scheduler.
Click Find. The details of the predefined scheduled tasks are displayed on two different tabs.
Enter a number in the Max Retries field. This number represents the number of times Oracle Identity Manager should attempt to complete the task before assigning the ERROR
status to the task.
Ensure that the Disabled and Stop Execution check boxes are cleared.
In the Start region, double-click the Start Time field. From the date-time editor that is displayed, set the date and time at which you want the task to run.
In the Interval region, set the following schedule parameters:
To set the task to run on a recurring basis, select the Daily, Weekly, Recurring Intervals, Monthly, or Yearly option.
If you select the Recurring Intervals option, then you must also specify the time interval at which you want the task to run on a recurring basis.
To set the task to run only once, select the Once option.
Provide values for the attributes of the scheduled task. Refer to the following table for information about the values to be specified.
Attribute Name | Description | Sample Value |
---|---|---|
Server |
Name of the IT Resource | ClearTrustITResource |
Target System CT Recon - Resource Object name |
Name of the target system parent resource object | ClearTrust |
Trusted Source Recon - Resource Object name |
Name of the Oracle Identity Manager resource object | The default value is Xellerate User |
Paging Range |
Paging range to extract user accounts from the target system | 10 |
TrialRecNum |
In case the user does not want to do a complete scheduled reconciliation and quickly want to check connectivity with the target and reconcile few records to ensure that reconciliation with the relevant target is working, this parameter could be used. The number of records, to be reconciled (ONLY) could be mentioned here. | 3 |
UseReconFieldMap |
This attribute is for the Client Customize reconciliation activity. The Client Customize reconciliation is activated and the fields in the Attribute Name: CTReconciliationFields lookup are reconciled if this attribute is set to true. Otherwise, all the available fields are reconciled. |
True |
CTReconciliationFields |
This lookup definition stores the reconciliation fields data that is used in customized reconciliation. | Lookup.CTReconciliation.FieldMap |
See Also:
Oracle Identity Manager Design Console Guide for information about adding and removing task attributesClick Save. The scheduled task is created. The INACTIVE
status is displayed in the Status field, because the task is not currently running. The task is run at the date and time that you set in Step 7.
Repeat Step 5 through 10 to define the second scheduled task.
The following adapters are imported into Oracle Identity Manager when you import the connector XML file. You must compile these adapters before you can use them to provision accounts on the target system.
CTUpdateUserProperty
CTUpdateGroup
CTStringTask
CTModifyUser
CTDeleteUser
CTDeleteGroup
CTCreateUser
CTAssign Default Group
CTAddGroup
CTPrepopStartDate
CTPrepopString
CTPrepopDateAddOneYear
CTEmailValidation
CTAdd Default Group to User
CTEndOrPwdExpDateValidatio
To compile adapters by using the Adapter Manager form:
Open the Adapter Manager form.
To compile all the adapters that you have imported into the current database, select the Compile All option.
To compile multiple (but not all) adapters, select the adapters you want to compile. Then, select the Compile Selected option.
Note:
Click Compile Previously Failed to recompile only those adapters that were not compiled successfully. Such adapters do not have anOK
compilation status.Click Start. Oracle Identity Manager compiles the adapters that you specify.
To view detailed information about an adapter:
Highlight the adapter in the Adapter Manager form.
Double-click the row header of the adapter, or right-click the adapter.
Select Launch Adapter from the shortcut menu that is displayed. Details of the adapter are displayed.