When you deploy the Identity Manager Driver for Linux and UNIX, you are required to select a provisioning option. The bi-directional driver option enables you to integrate the NIS user management system—commonly used in UNIX environments—with Novell® eDirectory™. As user information is added, modified or deleted in eDirectory, the bi-directional driver ensures that all changes are reflected in any connected NIS database or management files. Likewise, as NIS database information is added, modified or deleted, the bi-directional driver seamlessly and automatically updates eDirectory.
Identity Manager Driver for Linux and UNIX supports the NIS and NIS+ databases as well as the /etc/passwd and /etc/group files—all methods of managing UNIX users. This driver also runs on the following platforms:
- Solaris Sparc 2.8, 2.9 or 2.10
- Red Hat Linux AS 2.1, 3 or 4
- IBM AIX 5.1, 5.2 and 5.3
The bi-directional driver greatly simplifies the process of adding new users to your network. It provides support for generating default user and group IDs—as well as home directories—when a new user or group is created in eDirectory and synchronized to the NIS databases. And with some customization, the driver can also generate default passwords for new users. When combined, all of these features allow new users to log in without any intervention from the NIS database administrator.
Using the nxdrv-config Command#ou can use /usr/sbin/nxdrv-config to change the driver shim configuration. When you run this command, you are prompted for the function to perform.
> nxdrv-config Which configuration do you want to perform? 1) Set the Remote Loader and Driver object passwords 2) Configure the driver for Secure Sockets Layer (SSL) 3) Configure the driver to allow for remote client publishing, such as NIS or NIS+ clients 4) Extend the schema for Identity Manager (must be run on a Metadirectory server) 5) Configure PAM for publishing password changes 6) Configure LAM for publishing password changes Select one configuration option [q/?]:
PAM Integration#PAM integration is used to allow password changes on the platform to be published back to eDirectory.
No PAM authentication is provided by this connector. Note: the fan-out connector has these capabilities.