LDAP-UX Client Services B.05.01 Administrator Guide for HP directory servers and Windows ADS

Enter the password for the above user: [password not displayed] Enter

The installation now begins, followed by other related tasks; autosetup displays the progress

and results, as in the following example. As indicated, because an existing LDAP-UX configuration

profile does not exist, autosetup creates a new one. The profile and the associated LDAP-UX

domain will be based on the existing directory tree. In addition, autosetup provisions information

about the local host into the existing directory server.

* Extending schemas ... done.

No LDAP-UX Configuration Profile was found. Creating a new one.

* Downloading profile from DS ... done.

* Configuring ldapux_client.conf ... done.

* Provisioning LDAP-UX Client information into the Directory Server ... done.

* Setting up proxy user ... done.

* Configuring "/etc/nsswitch.conf" and "/etc/pam.conf" to use ldap ... done.

* Starting ldapclientd daemon ... done.

* Starting ldapcconfd ... done.

LDAP-UX was successfully configured.

NOTE: For more information about the configuration files created or modified by autosetup,

see “Samples of LDAP-UX configuration files created or modified by autosetup” (page 410). You

can display details about the LDAP-UX Client Services configuration by using the

/opt/ldapux/config/display_profile_cache command. For more information about

the use of this command, see Section 9.2.4 (page 280).

2.3.5.2 Automating Existing Directory Server Installation mode

For this mode of installation, you can run autosetup in silent mode and provide values for

parameters in the command line or with environment variables. As discussed in Section 2.3.5.1

(page 52), you must preestablish trust with the remote directory server by installing the CA certificate

before running autosetup. To perform this installation without user interaction, you must specify

the following in command-line options or environment variables:

The bind DN (the DN of the directory server user who can add the local host to the directory

server's LDAP-UX domain): use either the -D option or the LDAP_BINDDN variable.

The password used with the bind DN: use either -j option or the LDAP_BINDCRED variable.

The host name of the directory server being joined: use either -h option or the LDAP_HOSTPORT

variable.

In the following example, these parameters are specified in the command line:

# ./autosetup -h hpdhcalif -D "uid=domadmin,ou=people,dc=calif,dc=acme,dc=com" -j /tmp/jfile -q