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

9.5.3.2 Security
For security reasons, the LDAP administrator's password may not be specified on the command
line. It may be specified at the prompt (-w - option), in a file (-j <filename> option), or using the
LDAP_BINDCRED environmental variable described in Section 9.5.3.3 (page 364).
9.5.3.3 Environment variables
The ldapschema utility supports the following environment variables:
LDAP_BINDDN The distinguished name (DN) of an administrator who has permissions to read
and modify LDAP directory server schema.
LDAP_BINCRED The password for the privileged LDAP directory user.
LDAP_HOST The host name of the LDAP directory server. The LDAP_HOST variable uses
the “hostname:port” format. If the port is not specified, default port number is
389 for regular connections, or 636 for SSL connections.
Options specified on the command line override the values in environment variables. For example,
if the -j /home/secret.txt option is specified on the command line, and the LDAP_BINDCRED
environmental variable is set, the password of the LDAP directory server administrator is obtained
from the /home/secret.txt file.
9.5.3.4 Examples
This section describes examples using the ldapschema tool.
9.5.3.4.1 Example command for querying the schema status
The following command queries the status of RFC 2307 schema on Red Hat directory server,
ldaphost, with version 7.1:
ldapschema –q /etc/opt/ldapux/schema/rfc2307.xml -h ldaphost –T rhds
–V 7.1
The LDAP directory server version number bears no effect unless also specified in the XML files
being processed. Version specification must follow the same format as version specification used
in the /etc/opt/ldapux/schema/rfc2307.xml and /etc/opt/ldapux/map-rules.xml
files.
9.5.3.4.2 Example procedures for extending the new schema into the directory server
The following procedures are used to extend HP-UX Directory Server, ldaphost, with custom
Sample schema:
1. Create the schema definition file, /etc/opt/ldapux/schema/sample.xml, which contains
attribute type and object class definitions for the Sample schema.
2. This step is recommended. Query the current status of the Sample schema on the server by
running the following command:
ldapschema –q /etc/opt/ldapux/schema/sample.xml -h ldaphost
–T rhds –V 7.1 -D "<binddn>" -j /tmp/secret.txt
The administrator's password may be specified at the prompt (-w - option) or in a file (-j
<password_file> option).
3. Based on the results produced by Step 2, correct any invalid definitions.
4. Extend the HP-UX Directory Server schema with new Sample schema elements by executing
the following command:
ldapschema –e /etc/opt/ldapux/schema/sample.xml -h ldaphost
–T rhds –V 7.1 -D "<binddn>" -j /tmp/secret.txt
Note that LDAP directory server version number bears no effect unless also specified in the XML
files being processed. Version specification must follow the same format as version specification
364 Command and tool reference