System information

ManualsBrandsRed Hat ManualsComputer equipmentDIRECTORY SERVER 7.1 - GATEWAY CUSTOMIZATION

What’s New in This Release

Part Number 820-2952-10 Page 27

In addition, the following attributes are available from the SAP Resource adapter:

❍

Use SAP Temporary Passwords

❍

Return SAP Temporary Passwords on Failure

• The SAP Adapter now supports the Rename feature. For more information, see “Renaming

Accounts” on page 104 in Documentation Additions and Corrections. (ID-15582)

•The

rethrowAllSQLExceptions

parameter has been added to the Database Table adapter.

(ID-16419)

❍ If you select this option, exceptions with

ErrorCodes result.

❍ If you do not select this option, SQL statements that cause SQLExceptions with a

ErrorCode will catch and suppress the exception.

• The Oracle ERP adapter now has an

npw_number

account attribute to support contingent

workers. The

npw_number

account attribute functions in the same manner as

employee_number

, but the

employee_number

attribute and

npw_number

attribute are

mutually exclusive. If both are entered on create,

employee_number

takes precedence.

(ID-16507)

• Support for accessing Remedy servers has changed. The Sun Identity Manager Gateway no

longer depends on version 4.5 of the Remedy API libraries. Now, you must put Remedy

libraries in the Gateway directory (the Remedy libraries are located on the Remedy server).

For more information, see “Remedy” on page 104 in Documentation Additions and

Corrections. (ID-16551)

• It is now possible to specify the domain for an Active Directory resource in the resource

authentication properties. This makes it possible to limit a login module to authenticate

against just one domain. In a multi-domain AD environment, this prevents accounts from

being locked out due to failed login attempts. (ID-16603) To implement this feature, add the

following authentication property in the resource XML within the

element:

• Identity Manager can now use the Attachmate Adapter for Sun Java System Identity

Manager product to connect to mainframe resources. (ID-16631)

•The

checkIfUserExists

method now takes a

JCO.Client

argument, which gives you the

option of creating a new connection or using an existing one. A new connection is

necessary in cases where this method is not the first method performed on the connection.

The use of an existing connection is still provided for backward compatibility. In the

current version, only the rename operation uses this new functionality. (ID-16902)