LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Server Administrator's Guide (edition 8)
Table Of Contents
- LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Administrator's Guide
- Table of Contents
- Preface
- 1 Introduction
- 2 Installing LDAP-UX Client Services
- Before You Begin
- Summary of Installing and Configuring LDAP-UX Client Services
- Planning Your Installation
- Installing LDAP-UX Client Services on a Client
- Configuring Active Directory for HP-UX Integration
- Step 1: Install Active Directory
- Step 2: Install SFU 2.0, 3.0 or 3.5 including Server for NIS
- Step 3: Create a Proxy User
- Step 4: Add an HP-UX Client Machine Account to Active Directory
- Step 5: Use ktpass to Create the Keytab File for the HP-UX client machine
- Step 6: Add POSIX Attributes into the Global Catalog
- Importing Name Service Data into Your Directory
- Configuring LDAP-UX Client Services
- Step 1: Run the Setup Program
- Step 2: Install the PAM Kerberos Product
- Step 3: Configure Your HP-UX Machine to Authenticate Using PAM Kerberos
- Step 4: Configure the Name Service Switch (NSS)
- Step 5: Configure the PAM Authorization Service Module (pam_authz)
- Step 6: Configure the Disable Login Flag
- Step 7: Verify LDAP-UX Client Services for Single Domain
- Step 8: Configure Subsequent Client Systems
- Configuring the LDAP-UX Client Services with SSL or TLS Support
- Downloading the Profile Periodically
- 3 Active Directory Multiple Domains
- 4 LDAP-UX Client Services with AutoFS Support
- 5 LDAP Printer Configurator Support
- 6 Dynamic Group Support
- 7 Administering LDAP-UX Client Services
- Using the LDAP-UX Client Daemon
- Integrating with Trusted Mode
- SASL GSSAPI Support
- PAM_AUTHZ Login Authorization
- Policy And Access Rules
- How Login Authorization Works
- PAM_AUTHZ Supports Security Policy Enforcement
- Policy File
- Policy Validator
- Dynamic Variable Support
- Constructing an Access Rule in pam_authz.policy
- Static List Access Rule
- Dynamic Variable Access Rule
- Security Policy Enforcement with Secure Shell (SSH) or r-commands
- Adding Additional Domain Controllers
- Adding Users, Groups, and Hosts
- User and Group Management
- Displaying the Proxy User's Distinguished Name
- Verifying the Proxy User
- Creating a New Proxy User
- Displaying the Current Profile
- Creating a New Profile
- Modifying a Profile
- Changing Which Profile a Client is Using
- Creating an /etc/krb5.keytab File
- Considering Performance Impacts
- Client Daemon Performance
- Troubleshooting
- 8 Modifying User Information
- 9 Mozilla LDAP C SDK
- A Configuration Worksheet
- B LDAP-UX Client Services Object Classes
- C Command, Tool, Schema Extension Utility, and Migration Script Reference
- LDAP-UX Client Services Components
- Client Management Tools
- LDAP User and Group Management Tools
- Environment Variables
- Return Value Formats
- Common Return Codes
- The ldapuglist Tool
- The ldapugadd Tool
- The ldapugmod Tool
- The ldapugdel Tool
- The ldapcfinfo Tool
- LDAP Directory Tools
- Schema Extension Utility
- Name Service Migration Scripts
- Unsupported Contributed Tools and Scripts
- D Sample PAM Configuration File
- E Sample /etc/krb5.conf File
- F Sample /etc/pam.conf File for HP-UX 11i v1 Trusted Mode
- G Sample /etc/pam.conf File for HP-UX 11i v2 Trusted Mode
- H Sample PAM Configuration File for Security Policy Enforcement
- Glossary
- Index
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 /tmp/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 /tmp/secret.txt file.
Examples
This section describes examples using the ldapschema tool.
An Example for Querying the Schema Status
The following command queries the status of RFC 2307 schema on Windows 2003 Active Directory
Server, ldaphost:
ldapschema –q /etc/opt/ldapux/schema/rfc2307.xml -h ldaphost –T ads
–V 2003
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.
An Example for Extending the New Schema into the Directory Server
The following procedures are used to extend Windows 2003 Active 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 ads –V 2003 -D "<binddn>" -j /tmp/secret.txt
The administrator's password can be specified at the prompt (-w- option) or in a file (-j
<password_file>).
3. Based on the results produced by Step 2, correct any invalid definitions.
4. Extend the Active Directory Server schema with new Sample schema elements by executing
the following command:
ldapschema –e /etc/opt/ldapux/schema/sample.xml -h ldaphost
–T ads –V 2003 -D "<binddn>" -j /tmp/secret.txt
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/sample.xml,
/etc/opt/ldapux/schema/schema-ads.xml, and
/etc/opt/ldapux/schema/map-rules.xml files.
Schema Extension Utility 235