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
AutoFS Migration Scripts
This section describes the migration scripts which can be used to migrate your AutoFS maps
from files to LDIF files. After LDIF files are created, you can use the ldapmodify tool to import
LDIF files to your LDAP directory server. These migration scripts use the new automount schema
defined in RFC 2307-bis to migrate the AutoFS maps to LDIF. You need to import the new
automount schema into your LDAP directory server before you use these migration scripts to
migrate AutoFS maps.
Table 4-2 describes the migration scripts located in the /opt/ldapux/migrate/ads directory:
Table 4-1 Migration Scripts
DescriptionMigration Script
Migrates AutoFS maps from files to LDIF.
migrate_automount_ads.pl
Migrates AutoFS maps form the NIS server to LDIF.
migrate_nis_automount_ads.pl
Environment Variables
When you use the AutoFS migration scripts to migrate AutoFS maps, set the following
environment variables:
LDAP_BASEDN
The base distinguished name of the LDAP directory server that the AutoFS
maps are to be placed in.
NIS_DOMAINNAME
This variable specifies the fully qualified name of the NIS domain where
you want to migrate your data from. This variable is optional. If the NIS
domain name is not specified, LDAP-UX uses the value of the
NIS_DOMAIN parameter configured in the /etc/rc.conf.d/namesvrs
file.
This variable is only used by the migrate_nis_automount.pl script.
Examples
The following command sets the base DN to "dc=example, dc=hp, dc=com":
export LDAP_BASEDN="example.hp.com"
The following command sets the fully qualified name of the NIS domain to "example.hp.com":
export NIS_DOMAINNAME="example.hp.com"
68 LDAP-UX Client Services with AutoFS Support