| Oracle® Identity Manager Connector Guide for Microsoft Active Directory Release 9.0.3 Part Number B32355-02 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for Microsoft Active Directory Release 9.0.3 Part Number B32355-02 |
|
|
View PDF |
Deploying the connector involves the following steps:
If you want to configure the connector for multiple installations of Microsoft Active Directory, then perform the following procedure:
If you are going to install and use the password synchronization module for Microsoft Active Directory, then perform the following procedure:
If you are using Oracle Identity Manager release 9.0.1.3, then perform the following procedure:
The following table lists the deployment requirements for the connector.
| Item | Requirement |
|---|---|
| Oracle Identity Manager | Oracle Identity Manager release 8.5.3 or later |
| Target systems | Microsoft Active Directory Server (Microsoft Windows 2000 or 2003) |
| Target system host platforms | The target system host platform can be any one of the following:
|
| Other software | Certificate Services |
| External code | JNDI LDAP Booster package (ldapsdk-4.1.jar) |
| Target system user account | Microsoft Windows 2000/2003 Server (Domain Controller) administrator
You provide the credentials of this user account while performing the procedure in the "Defining IT Resources" section. |
You must ensure that the parent organization exists in the target server installation. The parent organization is specified as the value of the Root Context parameter in the relevant IT resource. Refer to the "Defining IT Resources" section for more information about this parameter.
The connector files and external code files to be copied and the directories to which you must copy them are given in the following table.
Note:
The directory paths given in the first column of this table correspond to the location of the connector files in the following directory on the installation media:Directory Servers\Microsoft Active Directory\Microsoft Active Directory Base
Refer to the "Files and Directories That Comprise the Connector" section for more information about these files.
| File in the Installation Media Directory | Destination Directory |
|---|---|
Files in the ext directory |
OIM_home\xellerate\ThirdParty
|
lib\xliActiveDirectory.jar |
OIM_home\xellerate\JavaTasks OIM_home\xellerate\ScheduleTask |
lib\xliADRecon.jar |
OIM_home\xellerate\JavaTasks OIM_home\xellerate\ScheduleTask |
Files in the resources directory |
OIM_home\xellerate\connectorResources
|
Files in the scripts directory |
OIM_home\xellerate\scripts
After you copy the install.bat (or install.sh) file, use a text editor to open the file and specify the actual location of the JDK directory in the file. |
Directories and files in the test directory |
OIM_home\xellerate\test
|
Files in the xml directory |
OIM_home\xellerate\XLIntegrations\ActiveDirectory\xml
|
Note:
While installing Oracle Identity Manager in a clustered environment, you copy the contents of the installation directory to each node of the cluster. Similarly, you must copy the
connectorResources directory and the JAR files to the corresponding directories on each node of the cluster.Configuring the Oracle Identity Manager server involves the following procedures:
Note:
In a clustered environment, you must perform this step on each node of the cluster.Changing to the required input locale (language and country setting) involves installing the required fonts and setting the required input locale.
To set the required input locale:
Note:
Depending on the operating system used, you may need to perform this procedure differently.Open Control Panel.
Double-click Regional Options.
On the Input Locales tab of the Regional Options dialog box, add the input locale that you want to use and then switch to the input locale.
Whenever you add a new resource bundle in the OIM_home\xellerate\connectorResources directory or make a change in an existing resource bundle, you must clear content related to connector resource bundles from the server cache.
To clear content related to connector resource bundles from the server cache:
In a command window, change to the OIM_home\xellerate\bin directory.
Enter one of the following commands:
Note:
You must perform Step 1 before you perform this step. If you run the command as follows, then an exception is thrown:OIM_home\xellerate\bin\batch_file_name
On Microsoft Windows:
PurgeCache.bat ConnectorResourceBundle
On UNIX:
PurgeCache.sh ConnectorResourceBundle
In this command, ConnectorResourceBundle is one of the content categories that you can remove from the server cache. Refer to the following file for information about the other content categories:
OIM_home\xellerate\config\xlConfig.xml
Note:
You can ignore the exception that is thrown when you perform Step 2.When you enable logging, Oracle Identity Manager automatically stores in a log file information about events that occur during the course of provisioning and reconciliation operations. To specify the type of event for which you want logging to take place, you can set the log level to one of the following:
ALL
This level enables logging for all events.
DEBUG
This level enables logging of information about fine-grained events that are useful for debugging.
INFO
This level enables logging of informational messages that highlight the progress of the application at coarse-grained level.
WARN
This level enables logging of information about potentially harmful situations.
ERROR
This level enables logging of information about error events that may still allow the application to continue running.
FATAL
This level enables logging of information about very severe error events that could cause the application to stop functioning.
OFF
This level disables logging for all events.
The file in which you set the log level and the log file path depend on the application server that you use:
For JBoss Application Server
To enable logging:
Add the following line in the OIM_home\xellerate\config\log.properties file:
log4j.logger.XELLERATE=log_level
In this line, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO
After you enable logging, log information is written to the following file:
JBoss_home\server\default\log\server.log
For IBM WebSphere:
To enable logging:
Add the following line in the OIM_home\xellerate\config\log.properties file:
log4j.logger.XELLERATE=log_level
In this line, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO
After you enable logging, log information is written to the following file:
WebSphere_home\AppServer\logs\server_name\startServer.log
For BEA WebLogic
To enable logging:
Add the following line in the OIM_home\xellerate\config\log.properties file:
log4j.logger.XELLERATE=log_level
In this line, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO
After you enable logging, log information is written to the following file:
WebLogic_home\user_projects\domains\domain_name\server_name\server_name.log
For OC4J
To enable logging:
Add the following line in the OIM_home\xellerate\config\log.properties file:
log4j.logger.XELLERATE=log_level
In this line, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO
After you enable logging, log information is written to the following file:
OC4J_home\opmn\logs\default_group~home~default_group~1.log
You must import the connector XML files in the following sequence:
xliADOrganizationObject_DM.xml
xliADGroupObject_DM.xml
xliADUserObject_DM.xml
XliActiveDirectoryScheduleTask_DM.xml
Caution:
If you do not import the connector files in the specified sequence, then the connector may not work.To import the connector XML files 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 xliADOrganizationObject_DM.xml file, which is in the OIM_home\xellerate\XLIntegrations\ActiveDirectory\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 AD Server IT resource is displayed.
Specify values for the parameters of the AD Server IT resource. Depending on whether the operating system is Microsoft Windows 2000 or Microsoft Windows 2003, refer to the appropriate 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 AD Server 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. Remove these nodes by right-clicking each node and then selecting Remove.
Click Import. The connector file is imported into Oracle Identity Manager.
Perform the same procedure to import the remaining connector XML files, in the specified order.
Note:
The IT resources that you must define are the same, regardless of the XML file that you import. Therefore, you only need to define the IT resources for the first XML file that you import.After you import the connector XML file, proceed to the "Step 6: Configuring Reconciliation" section.
This section provides IT resource parameter values for the following operating systems:
The following table provides values for the parameters of the AD Server IT resource, for Microsoft Windows 2000.
| Parameter | Description |
|---|---|
Admin FQDN |
Fully qualified domain name corresponding to the administrator
Format: Sample value: |
Admin Login |
User ID of the administrator account that is used to create the OU/user |
Admin Password |
Password of the administrator account that is used to create the OU/user |
Root Context |
This is the fully qualified domain name of the parent or root organization.
For example, the root suffix. Format: Sample value: |
Server Address |
Host name or IP address of the target Microsoft Windows 2000 computer on which Microsoft Active Directory is installed
Sample value: |
Last Modified Time Stamp |
Date and time at which the last AD User reconciliation run was completed
The reconciliation engine automatically fills a value in this attribute each time it runs the AD User reconciliation. Default value: |
Last Modified Time Stamp Group |
Date and time at which the last AD Group reconciliation run was completed
The reconciliation engine automatically fills a value in this attribute each time it runs AD Group reconciliation. Default value: |
Use SSL |
Specifies whether or not to use SSL to secure communication between Oracle Identity Manager and Microsoft Active Directory
Default value: See Also: The Known Issues list in Chapter 4 for information about a limitation arising from setting this parameter to Note: It is recommended that you enable SSL to secure communication with the target system. |
SSL Port Number |
Port at which SSL is running on the Microsoft Active Directory server
Default value: |
AtMap ADUser |
Attribute map name for the Microsoft Active Directory user
Default value: |
AtMap Group |
Attribute map name for the Microsoft Active Directory group
Default value: |
Target Locale: Country |
Country code
Default value: Note: You must specify the value in uppercase. |
Target Locale: Language |
Language code
Default value: Note: You must specify the value in lowercase. |
CustomizedReconQuery |
Specify the LDAP query that you want to use to customize reconciliation. The reconciliation engine uses this LDAP query to filter the records that must be fetched from the target system.
Sample value: Note: You can use this value in conjunction with the |
ADDisableAttr Lookup Definition |
Specify the name of the lookup table that lists the nonmandatory user attributes defined in Microsoft Active Directory. This attribute is used in conjunction with the Use Disable Attr parameter.
Note: Nonmandatory attributes of Microsoft Active Directory can accept Refer to Oracle Identity Manager Design Console Guide for information about creating the lookup definition. |
Use Disable Attr |
Specifies whether or not nonmandatory attributes defined in Microsoft Active Directory must be set to NULL when a user is disabled through a provisioning operation. The value of this parameter can be True or False. The default value is False.
Note: You can use this parameter only if you specify a value for the |
AD Sync installed (yes/no) |
If you are going to install and use the Microsoft Active Directory Password Synchronization module, then specify yes as the value of this parameter. Otherwise, specify no. The default value is no. |
OIM User UDF |
Specify the name of the user-defined field that you create in Oracle Identity Manager.
You must specify a value for this parameter only if you specify Note: You must specify the column name and not the field label that you enter while adding the custom attribute in Oracle Identity Manager. For example, if you enter the label |
Custom Attribute Name |
Specify the name of the custom attribute that you create in Microsoft Active Directory.
You must specify a value for this parameter only if you specify |
After you specify values for these IT resource parameters, proceed to Step 9 of the procedure to import connector XML files.
The following table provides values for the parameters of the AD Server IT resource, for Microsoft Windows 2003.
| Parameter | Description |
|---|---|
Admin FQDN |
Fully qualified domain name corresponding to the administrator
Format: Sample value: |
Admin Login |
User ID of the administrator account that is used to create the OU/user |
Admin Password |
Password of the administrator account that is used to create the OU/user |
Root Context |
Usually, this is the fully qualified domain name of the parent or root organization.
For example, the root suffix. Format: Sample value: |
Server Address |
Host name or IP address of the target Microsoft Windows 2000 computer on which Microsoft Active Directory is installed
Sample value: |
Last Modified Time Stamp |
Date and time at which the last AD User reconciliation run was completed
The reconciliation engine automatically fills a value in this attribute each time it runs the AD User reconciliation. Default value: |
Last Modified Time Stamp Group |
Date and time at which the last AD Group reconciliation run was completed
The reconciliation engine automatically fills a value in this attribute each time it runs AD Group reconciliation. Default value: |
Use SSL |
Specifies whether or not to use SSL to secure communication between Oracle Identity Manager and Microsoft Active Directory
Default value: See Also: The Known Issues list in Chapter 4 for information about a limitation arising from setting this parameter to Note: It is recommended that you enable SSL to secure communication with the target system. |
SSL Port Number |
Port at which SSL is running on the Microsoft Active Directory server
Default value: |
AtMap ADUser |
Attribute map name for the Microsoft Active Directory user
Default value: |
AtMap Group |
Attribute map name for the Microsoft Active Directory group
Default value: |
Country |
Country code
Default value: Note: You must specify the value in uppercase. |
Language |
Language code
Default value: Note: You must specify the value in lowercase. |
CustomizedReconQuery |
Specify the LDAP query that you want to use to customize reconciliation. The reconciliation engine uses this LDAP query to filter the records that must be fetched from the target system.
Sample value: Note: You can use this value in conjunction with the GroupObject attribute defined in the "User Reconciliation Scheduled Task" section. |
ADDisableAttr Lookup Definition |
Specify the name of the lookup table that lists the nonmandatory user attributes defined in Microsoft Active Directory. This attribute is used in conjunction with the Use Disable Attr parameter.
Note: Nonmandatory attributes of Microsoft Active Directory can accept Refer to Oracle Identity Manager Design Console Guide for information about creating the lookup definition. |
Use Disable Attr |
Specifies whether or not nonmandatory attributes defined in Microsoft Active Directory must be set to NULL when a user is disabled through a provisioning operation. The value of this parameter can be True or False.
Note: You can use this parameter only if you specify a value for the |
AD Sync installed (yes/no) |
If you are going to install and use the Microsoft Active Directory Password Synchronization module, then specify yes as the value of this parameter. Otherwise, specify no. The default value is no. |
OIM User UDF |
Specify the name of the user-defined field that you create in Oracle Identity Manager.
You must specify a value for this parameter only if you specify Note: You must specify the column name and not the field label that you enter while adding the custom attribute in Oracle Identity Manager. For example, if you enter the label |
Custom Attribute Name |
Specify the name of the custom attribute that you create in Microsoft Active Directory.
You must specify a value for this parameter only if you specify |
After you specify values for these IT resource parameters, proceed to Step 9 of the procedure to import connector XML files.
The scheduled tasks for reconciliation are created when you import the XliActiveDirectoryScheduleTask_DM.xml file as part of the procedure described in the "Step 5: Importing the Connector XML Files" section.
Additional tasks that you need to perform to configure reconciliation are described in the following sections:
If you are using Oracle Identity Manager release 9.0.1, then you must perform the following procedure to enable reconciliation:
You can select the fields that must be reconciled. To do this:
Open the Oracle Identity Manager Design Console.
Expand the Xellerate Administration folder.
Double-click Lookup Definition.
Search for the Lookup.ADReconciliation.FieldMap lookup definition by entering the name in the Code field and then clicking the Query icon.
To open the Lookup.ADReconciliation.FieldMap field map, double-click Lookup.ADReconciliation.FieldMap.
Add the required fields to the Lookup.ADReconciliation.FieldMap field map.
The following fields are provided by default in the Lookup.ADReconciliation.FieldMap field map:
memberOf
instanceType
Organization
givenName
sAMAccountName
IT Resource
objectGUID
name
password
Note:
The connector does not reconcile and store passwords in Oracle Identity Manager. Refer to Chapter 4, "Known Issues" for an explanation of this functionality of the connector.sn
cn
whenChanged
distinguishedName
initials
displayName
Note:
ThewhenChanged field is a mandatory field, which means that it must be present in the field map.Note:
Perform this step of the procedure only if you want to configure trusted source reconciliation. Only one connector can be configured for trusted source reconciliation. If you configure trusted source reconciliation for this connector while you have another trusted source configured, then both connector reconciliations would stop working.Refer to Oracle Identity Manager Connector Framework Guide for conceptual information about reconciliation configurations.
Use the Oracle Identity Manager Design Console to configure trusted source reconciliation as follows:
In the Resource Objects form, select the fields that you want to reconcile as follows:
Expand the Resource Management folder.
Double-click Resource Objects.
Enter Xellerate User in the Name field and then click the Query icon.
Double-click Xellerate User in the list that is displayed.
On the Object Reconciliation tab, add reconciliation fields as required. You must add all the reconciliation fields that are required to provide input for mandatory fields on the Xellerate User form, for example, fields such as User Login and First Name. However, you need not specify a value in the Password field, although it is a mandatory field.
In the Process Definition form, create reconciliation field mappings as follows:
Expand the Process Management folder.
Double-click Process Definition.
Enter Xellerate User in the Name field and then click the Query icon.
On the Reconciliation Field Mappings tab, add reconciliation field mappings as required. All the mandatory fields of the User Defined process form must be mapped.
In the Reconciliation Rules form, create a rule for the Xellerate User object as follows:
Expand the Development Tools folder.
Double-click Reconciliation Rules.
Create a rule for the Xellerate User object, with a rule element as required.
See:
Oracle Identity Manager Design Console Guide for instructionsSelect the Active check box to enable the rule.
To create the reconciliation scheduled tasks:
Expand the Xellerate Administration folder.
Select Task Scheduler.
Click Find. The details of the predefined scheduled tasks are displayed on two different tabs.
For the first scheduled task, enter a number in the Max Retries field. This number represents the number of times Oracle Identity Manager must attempt to complete the task before assigning the ERROR status to the task.
Ensure that the Disabled and Stop Execution check boxes are not selected.
In the Start region, double-click the Start Time field. From the date-time editor that is displayed, select 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 "Specifying Values for the Scheduled Task Attributes" section for information about the values to be specified.
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 Steps 5 through 10 to define the second scheduled task.
After you define both scheduled tasks, proceed to the "Enabling Reconciliation in Oracle Identity Manager Release 9.0.1" section.
This section provides information about the attribute values to be specified for the following scheduled tasks:
You must specify values for the following attributes of the lookup fields reconciliation scheduled task.
Note:
Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.After you specify values for these scheduled task attributes, proceed to Step 10 of the procedure to create scheduled tasks.
You must specify values for the following attributes of the user reconciliation scheduled task.
Note:
Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change. Refer to Appendix B for more information about these attributes.After you specify values for these scheduled task attributes, proceed to Step 10 of the procedure to create scheduled tasks.
If you are using Oracle Identity Manager release 9.0.1, then you must perform the following procedure to enable reconciliation:
See Also:
Oracle Identity Manager Design Console GuideOpen the Design Console.
Expand the Process Management folder.
Open the Process Definition form for the AD User.
Click the Reconciliation Field Mappings tab.
For each field that is of the IT resource type:
Double-click the field to open the Edit Reconciliation Field Mapping window for that field.
Deselect Key Field for Reconciliation Matching.
The following adapters are imported into Oracle Identity Manager when you import the connector XML file:
Chk Process Parent Org
AD Move OU
AD Get USNChanged
AD Get OU USNCR
Update AD Group Details
Get Group ObjectGUID Created
AD Delete Group
AD Create Group
Prepopulate AD Group Display Name
Prepopulate AD Group Name
check process organization
AD Set User Password
AD Set User CN Standard
AD Set Account Exp Date
AD remove User From Group
AD Pwd Never Expires
AD Must Change PWD
AD Move User New
AD Move User
AD Get ObjectGUID
AD Enable User
AD Disable User
AD Delete User
AD Create User
AD Change Attribute
AD Add User To Group
AD Prepopulate User Last Name
AD Prepopulate User Login
AD Prepopulate User Full Name
AD Prepopulate User Middle Name
AD Prepopulate User First Name
You must compile these adapters before you can use them to provision accounts on the target system.
To compile adapters by using the Adapter Manager form:
Open the Adapter Manager form.
To compile all the adapters that you import into the current database, select Compile All.
To compile multiple (but not all) adapters, select the adapters you want to compile. Then, select Compile Selected.
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 selected adapters.
If Oracle Identity Manager is installed in a clustered environment, then copy the compiled adapters from the OIM_home\xellerate\Adapter directory to the same directory on each of the other nodes of the cluster. If required, overwrite the adapter files on the other nodes.
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.
Note:
This is an optional step of the deployment procedure.This section covers the procedure to enable SSL on Microsoft Active Directory.
To configure SSL connectivity between Oracle Identity Manager and the target Microsoft Active Directory server, you must perform the following tasks:
The connector requires Certificate Services to be running on the host computer. To install Certificate Services:
Insert the operating system installation media into the CD-ROM or DVD drive.
Click Start, Settings, and Control Panel.
Double-click Add/Remove Programs.
Click Add/Remove Windows Components.
Select Certificate Services.
Follow the instructions to start Certificate Services.
The target Microsoft Active Directory server must have LDAP over SSL (LDAPS) enabled. To enable LDAPS, generate a certificate as follows:
Note:
Use the Enterprise CA option when you perform the following steps.On the Active Directory Users and Computers console, right-click the domain node, and select Properties.
Click the Group Policy tab.
Select Default Domain Policy.
Click Edit.
Click Computer Configuration, Windows Settings, Security Settings, and Public Key Policies.
Right-click Automatic Certificate Request Settings, and then select New and Automatic Certificate Request. A wizard is started.
Use the wizard to add a policy with the Domain Controller template.
At the end of this procedure, the certificate is created and LDAP is enabled using SSL on port 636.
If the Microsoft Active Directory certificate is not issued or certified by a certification authority (CA), then set it up as a trusted certificate. To do this, you first export the certificate and then import it into the keystore of the Oracle Identity Manager server as a trusted CA certificate.
To export the Microsoft Active Directory certificate:
Click Start, Programs, Administrative Tools, and Certification Authority.
Right-click the Certification Authority that you create, and then select Properties.
On the General tab, click View Certificate.
On the Details tab, click Copy To File.
Use the wizard to create a certificate (.cer) file using base-64 encoding.
To import the Microsoft Active Directory certificate into the certificate store of the Oracle Identity Manager server:
Note:
In a clustered environment, you must perform this procedure on all the nodes of the cluster.Copy the certificate to the Oracle Identity Manager server.
If you use IBM WebSphere, then you must also copy the following files:
For a nonclustered configuration of IBM WebSphere:
Copy the jsse.jar file into the WS_home\java\jre\lib\ext directory.
For a clustered configuration of IBM WebSphere:
Copy the jnet.jar, jsse.jar, and jcert.jar files into the WS_home\java\jre\lib\ext directory.
You can download these JAR files from the Sun Web site at
Change to the directory where you copy the certificate file, and then enter a command similar to the following:
keytool -import -alias alias -file cer_file -keystore my_cacerts -storepass password
In this command:
alias is the alias for the certificate (for example, the server name)
cer_file is the full path and name of the certificate (.cer) file
my_cacerts is the full path and name of the certificate store (the default is cacerts)
The path of the certificate store depends on the application server as shown in the following table.
| Application Server | Certificate Store Location |
|---|---|
| JBoss Application Server |
JBoss_home\jre\lib\security\cacerts
|
| BEA WebLogic |
BEA_home\java\jre\lib\security\cacerts
|
| IBM WebSphere | For a nonclustered configuration of IBM WebSphere, you must import the files into the following certificate stores:
WS_home\java\jre\lib\security\cacerts
For a clustered configuration of IBM WebSphere, you must import the files into the following certificate stores on each node of the cluster: WS_home\java\jre\lib\security\cacerts WS_home\etc\DummyServerTrustFile.jks |
| Oracle Containers for J2EE (OC4J) |
OC4J_home\jdk\jre\lib\security\cacerts
|
password is the keystore password (the default is changeit)
For example:
keytool -import -alias thorADCert -file c:\thor\ActiveDir.cer -keystore C:\mydir\java\jre\lib\security\cacerts -storepass changeit
Note:
changeit is the default password for the cacerts file stored in the Sun JVM. This may change depending on the JVM that you are using.In the command prompt window, when you are prompted to specify whether or not you want to trust this certificate, enter YES.
To confirm whether or not the certificate has been imported successfully, enter a command similar to the following:
keytool -list -alias alias -keystore mycacerts -storepass password
In the example given in Step 2, to confirm that the certificate has been successfully imported, use the following command and look for the certificate name (thorADCert) that you provide while importing the certificate into the keystore:
keytool -list -alias thorADCert -keystore C:\mydir\java\jre\lib\security\cacerts -storepass changeit
Perform this step only if you are registering the certificate file in a new certificate store.
Add the following line in the jre\lib\security\java.security file:
security.provider.N=com.sun.net.ssl.internal.ssl.Provider
In this line, N is any number that is not used in the file.
Restart the application server.
Note:
The user password cannot be set unless 128-bit SSL is used. In addition, the computer on which Microsoft Active Directory is installed must have Microsoft Windows 2000 Service Pack 2 (or later) or Microsoft Windows 2003 running on it.Note:
Perform this procedure only if you want to configure the connector for multiple installations of Microsoft Active Directory. Refer to Oracle Identity Manager Design Console Guide for detailed instructions on performing each step of this procedure.To configure the connector for multiple installations of the target system:
Create and configure one IT resource for each target system installation.
The IT Resources form is in the Resource Management folder. An IT resource is created when you import the connector XML file. You can use this IT resource as the template for creating the remaining IT resources, of the same resource type.
Configure reconciliation for each target system installation. Refer to the "Step 6: Configuring Reconciliation" section for instructions. Note that you only need to modify the attributes that are used to specify the IT resource and to specify whether or not the target system installation is to be set up as a trusted source.
You can designate either a single or multiple installations of Microsoft Active Directory as trusted sources.
If required, modify the fields to be reconciled for the Xellerate User resource object.
When you use the Administrative and User Console to perform provisioning, you can specify the IT resource corresponding to the Microsoft Active Directory installation to which you want to provision the user.
The connector for Microsoft Active Directory performs the following functions:
Updates Microsoft Active Directory with user account attributes (except for passwords) changed in Oracle Identity Manager
Updates Oracle Identity Manager with user account attributes (except for passwords) changed in Microsoft Active Directory
Updates Microsoft Active Directory with passwords changed in Oracle Identity Manager (requires LDAP over SSL)
The password synchronization module for Microsoft Active Directory updates Oracle Identity Manager with passwords changed in Microsoft Active Directory.
The connector is deployed on the Oracle Identity Manager server, and the module is deployed on the Microsoft Active Directory server. When they are deployed together (along with LDAP over SSL), the connector and the password synchronization module provide full, bidirectional synchronization of all user attributes, including passwords.
See Also:
Oracle Identity Manager Password Synchronization Module for Microsoft Active Directory Installation and Configuration GuideThe instructions in this section are aimed at solving a problem that was observed in the release 9.0.3 of the connector and password synchronization module.
You must create a custom attribute in Microsoft Active Directory to act as a flag for tracking password changes initiated by Oracle Identity Manager.
The following sections describe this procedure:
The Microsoft Active Directory Schema snap-in is required to create a custom attribute. Before you can create the custom attribute, you must ensure that this snap-in is installed.
To check if the snap-in is installed:
On the Microsoft Active Directory server, click Start and then click Run.
Enter the following command, and then click OK:
mmc /a
If the Microsoft Active Directory Schema snap-in is already installed, then its console is displayed when you run this command.
If the console is not displayed, then you must install the Microsoft Active Directory Schema snap-in as follows:
Log in to the Microsoft Active Directory server as the administrator.
Insert the Windows 2000 Server compact disc into your compact disc drive, and then click Browse this CD.
Double-click the I386 folder, double-click Adminpak, and then follow the instructions displayed in the Windows 2000 Administration Tools Setup Wizard.
Open the Microsoft Active Directory Schema snap-in console as follows:
Click Start, and then click Run.
Enter the following command, and then click OK:
mmc /a
On the Console menu, click Add/Remove Snap-in and then click Add.
Double-click Active Directory Schema, and then click Close.
To specify that you do not want to add any more snap-ins, click OK.
To save the changes that you make, click Save.
After you ensure that the Microsoft Active Directory Schema snap-in is installed, add the custom attribute in Microsoft Active Directory as follows:
Open the Active Directory Schema snap-in as follows:
On the Microsoft Active Directory server, click Start and then click Run.
Enter the following command, and then click OK:
mmc /a
In the console tree, right-click Attributes and then select Create Attribute.
Set the attribute type to Integer.
In the console tree, select Classes.
Right-click User, and then select Properties.
On the Attribute tab, select Add to add the attribute to the "User" class.
You must create a custom attribute in Oracle Identity Manager to act as a flag for tracking password changes initiated by Microsoft Active Directory.
To create a custom attribute (user-defined field) in Oracle Identity Manager:
See Also:
Oracle Identity Manager Design Console GuideOpen the Design Console.
Expand the Administration folder.
Select User Defined Field Definition.
Click the Search icon.
Select USR from the results that are displayed, and then click Add.
In the User Defined Fields dialog box, enter the following values:
Label: Enter a label for the field. For example: PWDCHANGEDINDICATION
Field Size: 20
The user-defined field that you create will hold either ADSYNC_TRUE or ADSYNC_FALSE.
DataType: String
Column Name: Enter a column name for the field.
It is recommended that you enter the same value as that you enter in the Label field. For example: PWDCHANGEDINDICATION
Oracle Identity Manager automatically appends USR_UDF_ to the column name that you specify. So, for example, if you specify PWDCHANGEDINDICATION as the column name, then the actual column name is changed to USR_UDF_PWDCHANGEDINDICATION.
Click Save.
While performing the procedure described in the "Defining IT Resources" section, you must specify values for the following parameters:
AD Sync installed (yes/no)
If you are going to install and use the Microsoft Active Directory Password Synchronization module, then specify yes as the value of this parameter. Otherwise, specify no. The default value is no.
OIM User UDF
Specify the name of the user-defined field that you create in Oracle Identity Manager.
You must specify a value for this parameter only if you specify yes as the value of the AD Sync installed (yes/no) parameter.
Note: You must specify the column name and not the field label that you enter while adding the custom attribute in Oracle Identity Manager. For example, if you enter the label PWDCHANGEDINDICATION, then the column name that you must specify is USR_UDF_PWDCHANGEDINDICATION. Oracle Identity Manager adds the USR_UDF_ prefix while creating a column.
Custom Attribute Name
Specify the name of the custom attribute that you create in Microsoft Active Directory.
You must specify a value for this parameter only if you specify yes as the value of the AD Sync installed (yes/no) parameter.
This section describes the sequence of events that take place during a password change operation.
Suppose user John Doe changes his password in Microsoft Active Directory. This events initiates the following sequence of events:
The password synchronization module changes the user's password in Oracle Identity Manager.
The password synchronization module changes the value of the Oracle Identity Manager user-defined field to ADSYNC_TRUE.
Because the value of the Oracle Identity Manager user-defined field is ADSYNC_TRUE, the Password Updated process task does not change the password in Microsoft Active Directory.
The password synchronization module changes the value of the Oracle Identity Manager user-defined field back to ADSYNC_FALSE.
Suppose user Jane Doe changes her password in Oracle Identity Manager. This event initiates the following sequence of events:
The Password Updated process task changes the user's password in Microsoft Active Directory.
The Password Updated process task changes the value of the Microsoft Active Directory custom attribute to 1.
Because the value of the Microsoft Active Directory custom attribute is 1, the password synchronization module does not change the password in Oracle Identity Manager.
The Password Updated process task changes the value of the Microsoft Active Directory custom attribute back to 0.
After you install the Microsoft Active Directory connector, you must make changes in the xlconfig.xml of the password synchronization to reflect the properties of the connector.
This is part of the installation procedure for the password synchronization module. It is described in the "Configuring the xlconfig.xml File After Installing the Connector" of Oracle Identity Manager Password Synchronization Module for Microsoft Active Directory Installation and Configuration Guide.
Note:
You must perform this procedure only if you are using Oracle Identity Manager release 9.0.1.3.In Oracle Identity Manager release 9.0.1.3, user accounts that are disabled or enabled are not reconciled correctly into Oracle Identity Manager during nontrusted (target resource) reconciliation. If you are using this release of Oracle Identity Manager, then you must perform the following procedure to resolve this problem:
Log in to the Design Console.
Create the userAccountControl reconciliation field in the AD User resource object as follows:
Expand the Resource Management folder.
Open the Resource Objects form.
Click the Search button.
From the list of resource objects that is displayed, double-click AD User.
On the Object Reconciliation tab, select the Reconciliation Fields tab.
On the Reconciliation Fields tab, click Add Field and then enter the following values:
Field Name: Enter userAccountControl.
Field Type: Select String.
Required: Select this check box.
Save the changes.
Map the userAccountControl reconciliation field to the OIM_OBJECT_STATUS field as follows:
Expand the Process Management folder.
Open the Process Definition form.
Click the Search button.
From the list of process definitions that is displayed, double-click the AD User process definition.
On the Reconciliation Field Mappings tab, double-click userAccountControl and then enter the following values:
Field Name: Select userAccountControl.
Field Type: Select String.
Process Data Field: Enter OIM_OBJECT_STATUS.
Save the changes.
