1 About the Connector

Oracle Identity Manager automates access rights management, security, and provisioning of IT resources. Oracle Identity Manager connectors are used to integrate Oracle Identity Manager with third-party applications. The connector for Novell eDirectory is used to integrate Oracle Identity Manager with Novell eDirectory.

Note:

Oracle Identity Manager connectors were referred to as resource adapters prior to the acquisition of Thor Technologies by Oracle.

This chapter contains the following sections:

Supported Functionality
Multilanguage Support
Reconciliation Module
Provisioning Module
Files and Directories That Comprise the Connector
Determining the Release Number of the Connector

Supported Functionality

The following table lists the functions that are available with this connector.

Process Task	Type	Description
Create User	Provisioning	Creates a user in Novell eDirectory
Delete User	Provisioning	Deletes a user in Novell eDirectory
Enable User	Provisioning	Enables a user in Novell eDirectory
Disable User	Provisioning	Disables a user in Novell eDirectory
Move User	Provisioning	Moves a user from one container to another in Novell eDirectory
Update User Password	Provisioning	Updates the password of a user in Novell eDirectory
Add User to Group	Provisioning	Adds a user to a group in Novell eDirectory
Remove User from Group	Provisioning	Removes a user from a group in Novell eDirectory
Assign Role to User	Provisioning	Assigns a role to a user in Novell eDirectory
Remove Assigned Role from User	Provisioning	Removes a role from a user in Novell eDirectory
Assign Trustee Right to User	Provisioning	Adds a trustee right to a user in Novell eDirectory
Remove Trustee Right from User	Provisioning	Removes a trustee right from a user in Novell eDirectory
Add Network Address Restriction to User	Provisioning	Adds a network address restriction to a user in Novell eDirectory
Remove Network Address Restriction from User	Provisioning	Removes a network address restriction from a user in Novell eDirectory
Create User	Reconciliation	Creates a user in Oracle Identity Manager
Delete User	Reconciliation	Deletes a user from Oracle Identity Manager
Enable User	Reconciliation	Enables a user in Oracle Identity Manager
Disable User	Reconciliation	Disables a user in Oracle Identity Manager
Move User	Reconciliation	Moves a user from one container to another in Oracle Identity Manager
Add User to Group	Reconciliation	Adds a user to a group in Oracle Identity Manager
Remove User from Group	Reconciliation	Removes a user from a group in Oracle Identity Manager
Assign Role to User	Reconciliation	Assigns a role to a user in Oracle Identity Manager
Remove Assigned Role from User	Reconciliation	Removes a role from a user in Oracle Identity Manager
Assign Trustee Right to User	Reconciliation	Adds a trustee right to a user in Oracle Identity Manager
Remove Trustee Right from User	Reconciliation	Removes a trustee right from a user in Oracle Identity Manager
Add Network Address Restriction to User	Reconciliation	Adds a network address restriction to a user in Oracle Identity Manager
Remove Network Address Restriction from User	Reconciliation	Removes a network address restriction from a user in Oracle Identity Manager

Multilanguage Support

In addition to English, this release of the connector supports the following languages:

French
Japanese

Reconciliation Module

This section discusses the elements that the reconciliation class extracts from the target system to construct reconciliation event records.

Reconciliation can be divided into the following types:

Lookup Fields Reconciliation
User Reconciliation

Lookup Fields Reconciliation

Lookup fields reconciliation involves reconciling group, role, and profile master data.

User Reconciliation

User reconciliation involves reconciling the fields discussed in this section.

Reconciled Resource Object Fields

The following fields are reconciled:

Note:

These fields do not have the ldap prefix.

User ID
First Name
Last Name
Middle Name
Department
Location
Telephone
Email
Communication Language
Timezone
Logon Script
Title
Profile
Organization Unit
Server Name
Security Group (multiple group names can be entered)
Role
- Role Name
- Scope
- Inheritance
Trustee Rights
- Property
- Supervisor
- Read
- Write
- Compare
- Add Self
Network Address (multiple group names can be entered)

Reconciled Xellerate User Fields

The following fields are reconciled only if reconciliation is implemented in trusted mode:

User ID
Password
Organization
First Name
Last Name
Xellerate Type
Role

Provisioning Module

The following fields are provisioned:

User ID
First Name
Last Name
Middle Name
Department
Location
Telephone
Email
Communication Language
Timezone
Logon Script
Title
Profile
Organization Unit
Server Name
Security Group
Role
- Role Name
- Scope
- Inheritance
Trustee Rights
- Property
- Supervisor
- Read
- Write
- Compare
- Add Self
Network Address

Files and Directories That Comprise the Connector

The files and directories that comprise this connector are compressed in the following ZIP file on the installation media:

Directory Servers\Novell eDirectory\Novell eDirectory Rev 2.2.0.zip

These files and directories are listed in the following table.

File in the Installation Media Directory	Description
xml\eDirResourceObject.xml	This XML file contains definitions for the following components of the connector: IT resource type Custom process form Process tasks and adapters (along with their mappings) Resource object Provisioning process Pre-populate rules Reconciliation process Lookup definitions
xml\eDirXLResourceObject.xml	This XML file contains the configuration for the Xellerate User. You must import this file only if you plan to use the connector in trusted source reconciliation mode.
lib\eDirProv.jar	This JAR file contains the class files required for provisioning and reconciliation.
Files in the `resources` directory	Each of these files contains locale-specific information that is used by the connector.
Files in the `troubleshoot` directory	These files are used to implement test cases that are run by using the troubleshooting utility.
docs\B32161_01.pdf	This guide, which provides instructions to deploy the connector.

Note:

The files in the troubleshoot directory are used only to run tests on the connector.

The "Step 2: Copying the Connector Files and External Code" section provides instructions to copy these files into the required directories.

Determining the Release Number of the Connector

You can determine the release number of the connector at any of the following stages:

Before Deployment

To determine the release number of the connector before you deploy it:

Extract the contents of the eDirProv.jar file. This file is in the lib directory inside the installation media directory.
Open the manifest.mf file in a text editor, which is one of the files bundled inside the eDirProv.jar file.

In the manifest.mf file, the release number of the connector is displayed as the value of the Version property.

Note:

If you maintain a copy of the eDirProv.jar file after deployment, you can use this method to determine the release number of the connector at any stage. However, after you deploy the connector, it is recommended that you use the After Deployment method.

During Deployment

To determine the release number of the connector while deploying the connector, refer to Step 4 of the procedure described in the "Step 4: Importing the Connector XML Files"section .

After Deployment

To determine the release number of the connector after deploying the connector: