Configuring Novell Nsure® Identity Manager 2 Driver 5.0 for PeopleSoft

Mark Worwetz

Senior Software Engineer

Novell, Inc.

mworwetz@novell.com

Integration Module for Enterprise

The PeopleSoft and SAP drivers are now available together in the NSure Identity Manager Integration Module for Enterprise:

Identity Manager Driver 3.6 for PeopleSoft

Identity Manager Driver 5.0 for PeopleSoft

Identity Manager Driver 1.0 for SAP HR

Identity Manager Driver 1.0 for User Management of SAP Software

Other ERP drivers will be packaged in this Integration Module as they are developed.

Enterprise Resource Planning

Software that is utilized or needed by most, if not all, organizations in the enterprise

Integrates various software modules into a single system.

High TCO - Very expensive package to purchase, deploy, and administrate

What is an ERP application?

Generic ERP Integration Issues

Driver Functionality

Identity Manager 2 Driver 5.0 for PeopleSoft

Driver Demonstration

Questions

Configuring Identity Manager 2
Driver 5.0 for PeopleSoft

Generic ERP Integration Issues

What is the goal of the integration?

Why integrate ERP data?

What data should be shared?

How should the data be accessed?

What are the risks of integration?

What is the Goal of the Integration?
Islands of isolated data

ERP

Database

Mail

PBX

Directory

Operating
System

ERP

PBX

Directory

Mail

Operating
System

Database

Identity Manager

What is the Goal of the Integration?
Sharing Data through the Enterprise

ERP system — employee and organization data

GroupWise® — e-mail address

Telecom — telephone number

Existing corporate directories — access, legacy resources

Facility database — office/mail-stop

Account Management – System Access rights

Etc.

What is the Goal of the Integration?
Authoritative Sources

Why Integrate ERP data?

Contains the most complete set of Identity data

Contains the most authoritative Identity data

Most protected source of data

What does Novell do for ERP?

Help leverage the investment in ERP by:

Integrating identity data with non-ERP applications

Provide data conversion opportunities

Allow access to ERP data outside of the ERP system

Provide multiple integration options from application-specific to generic interfaces

What Data Should Be Shared?

Only share data that is useful

Data that is duplicated in other applications

Data that is required to process business workflow

Data that must be accessed by non-ERP employees

Data that is shared beyond corporate boundary

Do not share sensitive information!

Make sure ERP administrators are involved in the decision.

How Should the Data be Accessed?

It is important that the customer is aware, and comfortable with, the integration access method

Direct System or Business Object APIs and Interfaces

Open Standard Protocols (LDAP, JDBC)

Flat file transfers (XML, CSV)

Make sure ERP administrators are involved in the decision!

Make sure appropriate rights are granted to provide the integration

What are the Risks of Integration?

API access introduces ERP system security concerns

DirXML® Driver acts as an ERP client – what rights should the driver have?

Are the authentication credentials protected?

Access to underlying data tables introduce data integrity and ERP system support issues.

Flat-file access introduces file-system security and resource issues.

Remote drivers introduce data transmission security issues.

What are the Risks of Integration?

Data integration introduces auditing concerns.

Improper planning and insufficient buy-in to the integration solution by all involved personnel is the NUMBER 1 problem in the field!

Always INVOLVE the ERP system administrators in the solution planning!

ERP Integration 'Bottom Line'

The ERP administrators are the only people who really understand the ERP system data and processes – you need their help!

The ERP administrators can make or break the project. Management is very dependent on their opinions – treat them with respect!

The ERP administrators are among the 'best and brightest' people at the customer site – discuss the function of the Identity Manager driver with them so they are comfortable with it.

Driver Functionality
Identity Manager Driver 5.0 for PeopleSoft

What is a driver?

What data is shared?

What is a driver?

A driver is composed of two distinct elements:

Driver Policies

The policies are default configuration information that describe the application connection information, schema mapping, and various data transformation policies

All policies are objects in the Identity Vault

Policies managed using iManager

Driver Shim

The shim is responsible for interfacing with the connected application and implementing policies

The shim is an independent code module

What data is shared?

Drivers are configured with an Employee focused scenario.

PeopleSoft drivers utilize an HR-derived staging table interface by default.

3.6 driver uses Message Agent interface – Publisher Primary

4.0 driver uses C++ Component Interface – Publisher Primary (phasing out)

5.0 driver uses Java Component Interface - Bi-directional

What data is shared?

Primary synchronized data object is a User in the Identity Vault

Personal Data

Address Data

Organizational Assignment and Hierarchy Data

Communication Data

Identity Manager 2 Driver 5.0 for PeopleSoft

Driver Design Features

Overview

PSA

Driver Policies

Publisher Channel

Subscriber Channel

Driver Configuration

Remote Loader Configuration

Deployment Notes

Demo

Driver Design Features
Identity Manager 2 Driver 5.0 for PeopleSoft

Works with 8.17 / 8.41 and later PeopleTools versions.

Written using Java – fully cross-platform wherever PSJOA is supported by PeopleSoft.

Utilizes standard PeopleSoft Component Interface integration technology.

Driver is application neutral. It can integrate with any standard Component Interface.

Full bi-directional capability.

Driver Design Features
Identity Manager 2 Driver 5.0 for PeopleSoft

Delivered with sample application and integration components (PSA). Requires no modification of existing business applications or server upgrade.

PSA implements a Transaction Record interface to ensure serialized processing and track modifications.

Able to process all events in chronological order (effective dating) as configured in PSA.

Supports Subscriber queries for all Level-0 fields in Data Component Interface (case-sensitive search optional)

Driver Design Features
Identity Manager 2 Driver 5.0 for PeopleSoft

May be implemented as a local or remote driver.

Must satisfy the customer!

All customers have unique requirements.

The driver can handle most issues via configuration and policies.

The driver functionality is periodically updated with new version and TID releases based 100% on real customer feedback.

The driver uses the “standard” Component Interface methods.

Create

Find

Get

Save

Cancel

Delete – Must be implemented by PeopleSoft developer

Overview
Identity Manager 2 Driver 5.0 for PeopleSoft

Driver must have connectivity to PeopleSoft Application Server in order to function. Driver acts as an administrative client.

Synchronous interface used for both Publisher and Subscriber channel.

For compatibility with prior 4.0 version, driver contains new parameters to allow/disallow Subscriber channel <add> and <delete> event handling.

Driver supports Application server connectivity failover.

Transaction model allows multiple drivers to process events.

Overview (continued)
Identity Manager 2 Driver 5.0 for PeopleSoft

DIRXML_TRANS01

DIRXML_S_PERS

Test Application Table

DIRXML_SCHEMA01

( CI )

etc.

New Person added to Test application

PSA Architecture: Publisher Events

OBject: P001

FIRST_NAME: Mark

LAST_NAME: Worwetz

...

OBject: P001

DIRXML_S_FN: Mark

DIRXML_S_LN: Worwetz

DIRXML_S_JOB: 0001

DIRXML_S_DEPTID: 0001

...

OBject: P001

DIRXML_S_FN: Mark

DIRXML_S_LN: Worwetz

DIRXML_S_JOB: 0001

DIRXML_S_JOB_DL: CEO

DIRXML_S_DEPTID: 0001

DIRXML_S_DEPT_DL: HR

DIRXML_S_DEPT

Test Dept Table

DIRXML_S_DEPTID: 0001

DIRXML_DESCR: HR

...

Data is synchronized to Staging Table using PeopleCode

Add Transaction created in DIRXML_TRANS01 Record using PeopleCode. Exposed in DIRXML_TRANS01 CI.

DIRXML_USERID: MWORWETZ

DIRXML_DN:

/Active/MWORWETZ

Driver retrieves transaction

Driver reads associated data record from staging table CI

Driver writes back

ectory naming attributes on new records.

COMMON_NAME: MWORWETZ

DISTINGUISHED_NAME:

/Active/MWORWETZ

Driver updates transaction status

DIRXML_STAGE01

( Record )

DIRXML_DRIVER: NPSDriver1P

DIRXML_EVENT: Add

DIRXML_ASSOC_ID: P001

DIRXML_STATUS: A -> I

...

DIRXML_DRIVER:NPSDriver1P

DIRXML_EVENT: ADD

DIRXML_ASSOC_ID: P001

DIRXML_STATUS : I -> S

( CI )

( Record )

1

2

3

7

4

5

6

DIRXML_TRANS01

DIRXML_S_PERS

Test Application Table

DIRXML_SCHEMA01

( CI )

etc.

PSA Architecture: Subscriber Events

OBject: P001

FIRST_NAME: Mark

LAST_NAME: Worwetz

TITLE_ID: 0001

DEPT_ID: 0001

COMMON_NAME: MWORWETZ

DISTINGUISHED_NAME: /Active/MWORWETZ

OBject: P001

DIRXML_S_FN: Mark

DIRXML_S_LN: Worwetz

DIRXML_S_JOB: 0001

DIRXML_S_DEPTID: 0001

...

OBject: P001

DIRXML_S_FN: Mark

DIRXML_S_LN: Worwetz

DIRXML_S_JOB: 0001

DIRXML_S_JOB_DL: CEO

DIRXML_S_DEPTID: 0001

DIRXML_S_DEPT_DL: HR

DIRXML_S_DEPT

Test Dept Table

DIRXML_S_DEPTID: 0001

DIRXML_DESCR: HR

...

Data is synchronized to data table CI using PeopleCode. EDirectory Naming attributes are not synced.

Transaction created in DIRXML_TRANS01 Record using PeopleCode. Exposed in DIRXML_TRANS01 CI.

DIRXML_USERID: MWORWETZ

DIRXML_DN:

/Active/MWORWETZ

Driver writes data to staging table CI. EDirectory Naming attributes added if needed.

DIRXML_STAGE01

( Record )

DIRXML_DRIVER: NPSDriver1S

DIRXML_EVENT: Add

DIRXML_ASSOC_ID: P001

DIRXML_STATUS: S

( CI )

( Record )

4

Driver ignores event due to driver identifier NPSDriver1S and status of 'S'

1

2

3

4

Schema Mapping Policy

Since driver interacts with a Component Interface for data, the name of the Component Interface is used as a “pseudo-class” specification.

Default driver configuration maps the eDirectory™ “User” class to the PeopleSoft Component Interface “DIRXML_SCHEMA01”

Driver Policies – Schema Mapping
Identity Manager 2 Driver 5.0 for PeopleSoft

DIRXML_SCHEMA01 Attr Name

COMMON_NAME

DESCRIPTION

FULL_NAME

FIRST_NAME

MIDDLE_NAME

EMAIL_ID

DEPT_LONG_DESCR

CITY

POSTAL

STATE

ADDRESS1

LAST_NAME

TITLE_LONG_DESCR

STATUS

MANAGER

MAIL_DROP

MANAGER_ID

ASSOC_ID

User Attr Name

CN

Description

Full Name

Given Name

Initials

Internet EMail Address

OU

Physical Delivery Office Name

Postal Code

S

SA

Surname

Title

employeeStatus

isManager

mailstop

managerWorkforceID

workforceID

Driver Policies – Schema Mapping
Identity Manager 2 Driver 5.0 for PeopleSoft

DIRXML_SCHEMA01 Attr Name

DEPT_ID

TITLE_ID

PHONE_BUSN

PHONE_HOME

PHONE_CELL

PHONE_PGR

DISTINGUISHED_NAME

User Attr Name

departmentNumber

jobCode

Telephone Number

homePhone

mobile

pager

Driver Policies – Schema Mapping
Identity Manager 2 Driver 5.0 for PeopleSoft

Driver Policies
Identity Manager 2 Driver 5.0 for PeopleSoft

Input Transformation Policy

Convert “MANAGER” values “Y” and “N” to boolean “true” and “false”.

Output Transformation Policy

Convert MANAGER boolean values “true” and “false” to “Y” and “N”.

Write “DISTINGUISHED_NAME” attribute to PeopleSoft when processing <modify> events with “from-merge” attribute set.

Write “COMMON_NAME” and “DISTINGUISHED_NAME” attributes to PeopleSoft after successful publication of events containing operation data.

Publishing PeopleSoft Data to Other Applications

Publisher Channel

IDM2 Remote

Loader Service

IDM2 Driver for

Application N

PeopleSoft Modules

Transactions

PeopleTools

Identity

Vault

PeopleSoft Host

PeopleSoft Client

IDM2 Remote

Loader Shim

IDM2

Engine

IDM2 Remote

Loader Service

Application Host

Application Host

Application Server

PeopleSoft

Component

Interface

IDM2 Driver

for

PeopleSoft

IDM2 Remote

Loader Service

IDM2 Driver for

Exchange

Data changes
from PeopleSoft application
modules are
logged

Configured to poll on specified intervals for data changes

Driver object containing
business policies and connection parameters

Driver
Requests Transactions

Driver receives data and transforms the relevant information into an XML document

Application N

Exchange

The driver updates
and retrieves data
in the application

FIN EPM CRM

HR SCM SA

etc.

IDM2 Engine processes data according to business policies

XML Doc

SSL Connection

IDM2 Engine adds or updates the data into Identity Vault

1

2

3

4

5

6

departmentNumber

employeeStatus

Full Name

Given Name

homePhone

Initials

isManager

jobCode

mailstop

managerWorkforceID

mobile

OU

pager

Physical Delivery Office Name

Postal Code

S

SA

Surname

Telephone Number

Title

workforceID

Default Publisher Filter
Identity Manager 2 Driver 5.0 for PeopleSoft

Matching Policy

Match object with same class and “workforceID”.

Create Policy

Attributes “Given Name” and “Surname” required.

Password set to value of “Surname” attribute.

CN generation: First Initial + Surname, no Suffix, all capitalized (ie. John Adams = JADAMS) Duplicates sequentially numbered (JADAMS2)

Default Publisher Policies
Identity Manager 2 Driver 5.0 for PeopleSoft

Placement Policy

Active Employees in specified “Active” container.

Inactive Employees in specified “Inactive” container.

“employeeStatus” set to “A” or “I” respectively.

Command Transformation Policy

All managers identified by “isManager” set to “true”.

Active managers added to specified “Manager Group”

Active employees added to specified “Employee Group”

Employees have “workforceID” of their manager in “managerWorkforceID” attribute.

Managers have DN of subordinates in “directReports” attribute.

Employees have DN of manager in “manager” attribute

Default Publisher Policies (cont.)
Identity Manager 2 Driver 5.0 for PeopleSoft

Maintaining Manager-Employee
Object Relationships in Identity Vault

Jack

directReports = Maria

Maria

manager = Jack

directReports = John

John

manager = Maria

Publisher Channel Functionality
Identity Manager 2 Driver 5.0 for PeopleSoft

Application data modifications invoke PeopleSoft code (PeopleCode) in the PSA to generate Transaction records.

The PSA transaction code organizes transactions into processing date order. Future-dated events are not processed until date is current or past.

Access to event information from PeopleSoft is via a Transaction Component Interface (CI). (DIRXML_TRANS01)

Driver polls the Transaction CI for records indicating “Available” transactions involving Add, Modify, or Delete of data records. Transaction record contains key of data record affected by transaction.

Publisher Channel Functionality
(continued)

Transaction state set to “In Process”. Key to data record and transaction ID is saved.

Access to PeopleSoft data records is via a Data CI. (DIRXML_SCHEMA)

Driver reads current data values of data record and Publishes event.

Event is processed by engine, status is returned to driver.

Transaction CI is utilized to update status in transaction record.

Subscribing Application Data to PeopleSoft

PeopleSoft Modules

Transactions

PeopleTools

Identity

Vault

PeopleSoft Host

PeopleSoft Client

IDM2 Remote

Loader Shim

IDM2

Engine

IDM2 Remote

Loader Service

Application Server

PeopleSoft

Component

Interface

IDM2 Driver

for

PeopleSoft

FIN EPM CRM

HR SCM SA

etc.

Data from other applications

XML Doc

XML Doc

SSL Connection

Data the PeopleSoft driver subscribes to that comes from other applications through Identity Manager

Driver posts incoming data to the Staging Table

Identity Manager Host

Subscriber Channel

Driver object containing
business policies and connection parameters

1

2

3

PeopleCode configured to consume data from the

Staging Table

4

CN

departmentNumber

Description

employeeStatus

Given Name

homePhone

Initials

Internet EMail Address

isManager (reset)

jobCode

mailstop

managerWorkforceID

mobile

pager

Physical Delivery Office Name

Postal Code

S

SA

Surname

Telephone Number

workforceID

Default Subscriber Filter
Identity Manager 2 Driver 5.0 for PeopleSoft

Default Subscriber Policies
Identity Manager 2 Driver 5.0 for PeopleSoft

Matching Policy

Match object with same class and “workforceID”.

Match on “Given Name” and “Surname”

Event Transformation Policy

Transform <move> event into modify of “DISTINGUISHED_NAME” attribute.

Transform <rename> event into modify of “CN” and “DISTINGUISHED_NAME” attributes.

Transform <delete> event into remove of “Subscriber-only” attributes “CN”, “DISTINGUISHED_NAME”, “Description, and “Internet EMail Address”. (Present for backwards compatibility with 4.0 driver - commented out)

Default Subscriber Policies (cont.)
Identity Manager 2 Driver 5.0 for PeopleSoft

Create Policy

Requires attributes required by the DIRXML_SCHEMA01 CI: “Given Name”, “Surname”, “jobCode”, “departmentNumber”, and “employeeStatus”.

Subscriber Channel Functionality
Identity Manager 2 Driver 5.0 for PeopleSoft

Driver uses Data CI to access records for <query> or <modify> events.

Creates new Data CI objects if configured to allow <add> events and Data CI implements “Create” method.

Deletes existing Data CI objects if configured to allow <delete> events and Data CI implements “Delete” method.

For all Data CI events the driver updates the data staging table. PeopleCode transfers modifications to appropriate application tables.

Driver Configuration Parameters
Connection Parameters

Authentication ID

The name of the PeopleSoft administrative user that will be used for all read and write operations to the PeopleSoft Application server.

Authentication Context

The DNS name or IP address and JOLT port of the target PeopleSoft Application server host system. Must be preceeded with '//' and contain a ':' delimiter. Multiple entries allowed for connectivity failover must be separated with ';'
(ie. //psofthost:9000;//backuphost:9000)

Application Password

Password of the administrative user.

Schema CI Name

The name of the PeopleSoft Component Interface used to read and write PeopleSoft data records (default: DIRXML_SCHEMA01). May be multiply defined to add additional data schemas

Data Record ID Field

The name of the PeopleSoft application data record primary key field (default: ASSOC_ID).

Use Case-Sensitive Search? (0/1)

Controls whether or not the driver evaluates search attribute matches using case-sensitive match criteria (default: 0 = false).

Driver Configuration Parameters
Driver Implementation Parameters

Allow 'add' events? (0/1)

Determines if the driver will process “add” events on the Subscriber channel. (option set during installation)

Data Record ID Field Default Value

Specifies the default value for the Schema CI primary key field. Only used for Subscriber channel “add” events. (default: NEW – matches PSA-defined default key value)

Allow 'delete' events? (0/1)

Determines if the driver will process “delete” events on the Subscriber channel. (option set during installation)

Driver Configuration Parameters
Subscriber Implementation Parameters

Transaction CI Name

The name of the Component Interface that is used to read and update PeopleSoft transaction records. (default: DIRXML_TRANS01)

Driver Subset Identifier

This field is a string used to match the driver to the transaction records it will process. (DIRXML_DRIVER field value in Transaction CI. Default: NPSDriver1)

Queue Poll Interval (seconds)

The time in seconds that the driver waits between requests for available transactions from the Transaction CI. (default: 5)

Driver Configuration Parameters
Publisher Implementation Parameters

DirXML Driver for PeopleSoft
Remote Loader Usage

Why use the Remote Loader?

Customer does not want driver on eDirectory Server.

Dedicated processing for the driver.

Dedicated tracing capability.

PeopleSoft with Remote Loader requirements

Host platform supporting JDK/JRE 1.4 or higher (IDM2 DR1 requirement)

PeopleTools PSJOA.jar installed on host platform

Remote Loader features

SSL connection security

Bi-directional password handshake

Do not remove or modify any fields of the Transaction CI. The driver depends on them. It is OK to add fields.

The “dirxmlcomps.jar” file contains all compiled CI code for the PSA. If other CIs are needed, follow Implementation Guide directions for generating, compiling, and packaging Java CI APIs.

All data events between the driver and the PSA utilize a staging table interface for sample integration purposes. However, the driver will interact with any CI supporting the required methods (ie. Directly to the DIRXML_TST_PERS CI in the PSA)

Driver Deployment Notes
Identity Manager 2 Driver 5.0 for PeopleSoft

The only “client” software required by the driver is the PSJOA.jar file for the appropriate release of PeopleTools (must match the version on the target Application Server)

Use CITester.class test program to validate connectivity, proper PSJOA.jar, and CI API availability.

The driver can only properly integrate with Component Interfaces with no more than 2 levels (base record and 0 or more level-1 scroll/collection records). An example is the DIRXML_TST_PERS with scroll record DIRXML_S_PHONES.

Scroll records will be represented in XDS as multi-valued attributes with named component values.

Driver Deployment Notes (cont.)
Identity Manager 2 Driver 5.0 for PeopleSoft

The driver implementation guarantees that all current attributes of an object are obtained during processing of any transaction on that object. If future-dating transactions, use effective-date on Data rows.

The “isManager” attribute utilizes the IDM2 DR1 “reset” functionality on the Subscriber channel. If set in eDirectory, the value will be reset to the value provided by PeopleSoft.

Derived/XLAT fields can not be subscribed, only published from PeopleSoft. The sample application includes:

DEPT_LONG_DESCR

TITLE_LONG_DESCR

Driver Deployment Notes (cont.)
Identity Manager 2 Driver 5.0 for PeopleSoft

The “Migrate into eDirectory” option is supported. Only level-0 field values used for matching.

Transaction records are generated by Publisher modifications made in PeopleSoft applications and by Subscriber modifications made by the driver.

Driver Deployment Notes (cont.)
Identity Manager 2 Driver 5.0 for PeopleSoft

Demo

Question and Answer

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

In a typical environment data is owned by different groups. Employee data is normally owned by HR exclusively.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The SAP solution does not require any customization to the SAP system. We utilized SAP’s technology and had our product Validated by SAP. When a product is validated by SAP– SAP certifies that our technology will work in a customers SAP environment.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

The Directory becomes the “hub” for all of the systems. It enables us to share information with systems that are otherwise desperate.

This allows the driver to make an association between a user object and the objects listed above. The driver can then populate attributes in the user object with meaningful data. For example, the attribute “Title” will be populated with “Pilot” rather than referencing a number as received from SAP. This also allows reporting relationships (i.e. manager and employee) to be established in eDirectory.

This allows the driver to make an association between a user object and the objects listed above. The driver can then populate attributes in the user object with meaningful data. For example, the attribute “Title” will be populated with “Pilot” rather than referencing a number as received from SAP. This also allows reporting relationships (i.e. manager and employee) to be established in eDirectory.

Micah Bauer

2004-03-05T11:21:14

Mark Worwetz