You can control the operation of the Linux and UNIX 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 LinuxUnix-IDM3_5_0-V2.xml over the existing driver. For details, see Section 3.6, 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 Linux or UNIX identity are not synchronized to the Identity Vault.
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 Linux and UNIX driver with the Identity Manager User Application. For more information about the User Application, see the User Application guides on the Novell® Identity Manager 3.6.1 Web site.
POSIX* Management Mode controls the management of RFC 2307 information, such as uidNumber, gidNumber, homeDirectory, and loginShell, for the driver.
Manage Bidirectional: Both the connected Linux or UNIX system and the Identity Vault can provide RFC 2307 information. Schema extensions to hold this information are required for Manage Bidirectional.
Manage Local: The local Linux or UNIX system manages RFC 2307 information. Schema extensions are not necessary with Manage Local, and the RFC 2307 information is not synchronized.
Manage from Identity Vault: The Identity Vault provides RFC 2307 information through a manual or automated process. Select this option if you are using centralized UID/GID management with the Linux and UNIX Settings driver. Schema extensions are required with Manage from Identity Vault.
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.
Database Type specifies the type of account management database that you use for your network-wide information storage.
Files: Local file-based storage (/etc/passwd)
NIS: Map-based storage
NIS+: Hierarchical domain-based storage.
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 removes home directories from the file system when users are deleted.
This option has no effect on AIX systems.
Specifies whether the driver automatically creates home directories in the file system when users are created.
This option has no effect on AIX systems. On AIX, the add-user.sh script uses the native AIX mkuser command. By default, this command creates a home directory. This setting is governed by /usr/lib/security/mkuser.default and /etc/security/login.cfg.
Specifies whether the driver allows duplicate UIDs on the connected Linux or UNIX system.
AIX does not allow duplicate UIDs. Select for AIX connected systems.
Specifies whether the driver allows duplicate GIDs on the connected Linux or UNIX system.
AIX does not allow duplicate GIDs. Select for AIX connected systems.
Specifies the number of seconds that the Publisher shim waits after running the polling script 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 |
|
|
|
|
|
|
|
|
|
|
|
|
The Linux or UNIX Connected System Accepts Passwords from the Identity Vault |
|
|
The Identity Vault Accepts Passwords from the Linux or UNIX Connected System |
|
|
The Identity Vault Accepts Administrative Password Resets from the Linux or UNIX 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.
This option does not apply if the POSIX Management Mode is set to Manage Local. When it does apply, it has the following effect:
It specifies whether the driver synchronizes the Group Membership attribute of a corresponding Group object in the Identity Vault (if one exists with that GID).
The driver always synchronizes a user’s GID number (primary group identification) to the RFC 2307 gidNumber attribute of the corresponding User object in the Identity Vault.
Specifies whether the driver excludes events for users and groups with a uidNumber or gidNumber less than 100.
This option does not apply if the POSIX Management Mode is set to Manage Local. When it does apply, it specifies whether the driver requires users and groups from the Identity Vault to have RFC 2307 information, such as uidNumber, gidNumber, and homeDirectory, before it provisions them to the connected Linux or UNIX system.
Specifies whether the driver creates the user gecos field from the First Name and Last Name attributes of the User object in the Identity Vault for subscribed events.
Specifies whether the driver uses lowercase for the CN of User and Group objects it receives in events from the Metadirectory engine.
Linux and UNIX user and group names are usually lowercase.
Specifies whether the driver allows passwords to flow from the Identity Vault to the connected Linux or UNIX system.
Specifies whether the driver allows passwords to flow from the connected Linux or UNIX system to the Identity Vault.
Specifies whether the driver allows passwords to be reset from the connected Linux or UNIX system in the Identity Vault. The root user can use the passwd command to set another user’s password.
Specifies whether the driver uses passwords from the connected Linux or UNIX system to set non-reversible NDS® passwords in the Identity Vault.
Specifies whether the driver uses passwords from the connected Linux or UNIX 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 Linux or UNIX 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