You can control the operation of the driver by modifying the properties described in the following sections.
IMPORTANT:Changing these values requires a restart of the driver.
To change import-only properties, you must re-import the driver configuration file over the existing driver. For details, see Section 3.5, Setting Up the Driver on the Metadirectory Server.
To edit the properties shown on the Driver Configuration page and the Global Configuration Values page:
In iManager, select from the Identity Manager task list on the left side of the window.
Navigate to your driver set by searching the tree or by entering its name.
Click the driver to open its overview.
Click the driver icon.
Select or as appropriate.
Edit the property values as desired, then click .
Properties that you can set only during driver import are used to generate policies and other configuration details.
Table 5-1 Driver Import-Only Parameters
|
Property Name |
Values or Format |
|---|---|
|
|
|
|
|
|
|
|
|
Bidirectional: Identities are synchronized from both the Identity Vault and the connected system (application). After all pending events are processed, the Identity Vault and connected system mirror each other.
Application to Identity Vault: Identities are synchronized from the connected system (application) to the Identity Vault, but not vice versa. For example, an identity created in the Identity Vault is not created on the connected system unless explicitly migrated.
Identity Vault to Application: Identities are synchronized from the Identity Vault to the connected system (application), but not vice versa. For example, changes made to a Top Secret identity are not synchronized to the Identity Vault.
Yes: Enables prompts for the default TSO account number, default TSO procedure, and the default TSO unit.
No: Disables prompts for the default TSO account number, default TSO procedure, and the default TSO unit.
Yes: Enables prompts for the UID and GID number assignment source (Top Secret or Identity Vault), the UID number range, the GID number range, the default home directory path, whether to create home directories, and the default program.
No: Disables prompts for the UID and GID number assignment source (Top Secret or Identity Vault), the UID number range, the GID number range, the default home directory path, whether to create home directories, and the default program.
Specifies whether the driver uses either Approval Flow or Role-Based Entitlements with the Entitlements Service driver.
Enable entitlements for the driver only if you plan to use the User Application or Role-Based Entitlements with the driver.
You can use Role-Based Entitlements to integrate the driver with the Identity Manager User Application. For more information about the User Application, see the User Application guides on the Novell® Identity Manager Web site.
Specifies whether the driver uses Secure Sockets Layer (SSL) to encrypt the connection between the Identity Vault and the application.
We strongly recommend that you use SSL. If you do not use SSL, identity data, including passwords, is sent across the network in clear text.
Table 5-2 Driver Configuration Page
The Driver object password is used by the driver shim (embedded Remote Loader) to authenticate itself to the Metadirectory engine. This must be the same password that is specified as the Driver object password on the connected system driver shim.
The Remote Loader Connection Parameters option specifies information that the driver uses for Secure Sockets Layer (SSL) communication with the connected system.
Table 5-3 Remote Loader Connection Parameters
The following is an example Remote Loader connection parameter string:
hostname=192.168.17.41 port=8090 kmo="SSL CertificateIP"
The Remote Loader password is used to control access to the driver shim (embedded Remote Loader). This must be the same password that is specified as the Remote Loader password on the connected system driver shim.
Specifies whether the driver shim discards events that would cause loopback conditions. This function supplements the loopback detection provided by the Metadirectory engine.
Specifies whether the driver automatically creates home directories in the hierarchical file system when users are created.
Specifies the data set name of the catalog used for new users created by the driver.
If you specify a value for , the REXX exec to add a new user issues the following command:
DEFINE ALIAS(NAME('user') RELATE('UserCatalogAlias'))
Specifies the data set name of the catalog used for new groups created by the driver.
If you specify a value for , the REXX exec to add a new group issues the following command:
DEFINE ALIAS(NAME('group') RELATE('GroupCatalogAlias'))
Specifies the number of seconds that the Publisher shim waits after running the polling exec and sending events from the change log to the Metadirectory engine. The default interval is 60 seconds.
Specifies whether the Publisher shim is active.
Select if you are using Identity Vault to Application (one-way) data flow. This saves processing time.
Specifies how often, in seconds, the driver shim contacts the Metadirectory engine to verify connectivity. Specify 0 to disable the heartbeat.
Table 5-4 Global Configuration Values
|
Property Name |
Values or Format |
|---|---|
|
Text value |
|
|
Text value |
|
|
Text value |
|
|
Text value |
|
|
Text value |
|
|
Text value |
|
|
Text value |
|
|
|
|
Numeric range |
|
|
Numeric range |
|
|
Text value |
|
|
Text value |
|
|
The Top Secret Connected System Accepts Passwords from the Identity Vault |
|
|
The Identity Vault Accepts Passwords from the Top Secret Connected System |
|
|
The Identity Vault Accepts Administrative Password Resets from the Top Secret Connected System |
|
|
|
|
|
|
Require Password Policy Validation before Publishing Passwords |
|
|
Reset User’s External System Password to the Identity Manager Password on Failure |
|
|
Notify the User of Password Synchronization Failure via E-Mail |
|
|
Identity Vault Container object |
|
|
Identity Vault Container object |
To view and edit Password Management GCVs, select for .
To view and edit User and Group Placement GCVs, select for .
Specifies the name of the driver. This value is used by the e-mail notification templates.
Specifies the ACID of a user to be used as a model for creating new users.
Specifies the default department for new users.
Specifies the default group for new users.
Specifies the default account number for new users.
Specifies the default cataloged procedure name for new users. For example, IKJACCNT.
Specifies the default unit name for new users. For example, SYSALLDA.
Specifies how UID and GID numbers are assigned to new users and groups. Select or .
Specifies a range of numbers used when Top Secret assigns UID numbers for new users. The REXX exec to add a new user uses this value with the RANGE keyword on the TSS command. Use a pair of values separated by a comma, similar to the following:
10000,200000
Specifies a range of numbers used when Top Secret assigns GID numbers for new groups. The REXX exec to add a new group uses this value with the RANGE keyword on the TSS command. Use a pair of values separated by a comma, similar to the following:
10000,200000
Specifies the default OMVS home directory path for new users. Include the ending slash (/) in the directory path. The user’s ACID is appended to the value that you specify. Use a value similar to the following:
/home/
In this example, the home directory that is assigned by the driver for a user whose ACID is IBMUSER is /home/IBMUSER.
Specifies the default OMVS program (login shell). Use a value similar to the following:
/bin/sh
Specifies whether the driver allows passwords to flow from the Identity Vault to the connected system.
Specifies whether the driver allows passwords to flow from the connected system to the Identity Vault.
Specifies whether the driver allows passwords to be reset from the connected system in the Identity Vault. An administrative user can use the TSS REPLACE command to set another user’s password.
Specifies whether the driver uses passwords from the connected system to set NDS® passwords in the Identity Vault. NDS passwords in the Identity Vault are not bidirectional and cannot be synchronized to another system.
Specifies whether the driver uses passwords from the connected system to set NMAS™ Distribution Passwords, which are used for Identity Manager password synchronization.
Specifies whether the driver applies NMAS password policies to published passwords. If so, a password is not written to the Identity Vault if it does not conform.
Specifies whether, on a publish Distribution Password failure, the driver attempts to reset the password on the connected system using the Distribution Password from the Identity Vault.
Specifies whether the driver sends an e-mail to a user if the password cannot be synchronized.
Specifies the base container object in the Identity Vault for user synchronization. This container is used in the Subscriber channel Event Transformation policy to limit the Identity Vault objects being synchronized. This container is used in the Publisher channel Placement policy as the destination for adding objects to the Identity Vault. Use a value similar to the following:
users.myorg
Specifies the base container object in the Identity Vault for group synchronization. This container is used in the Subscriber channel Event Transformation policy to limit the Identity Vault objects being synchronized. This container is used in the Publisher channel Placement policy as the destination when adding objects to the Identity Vault. Use a value similar to the following:
groups.myorg