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
Name Service Migration Scripts
This section describes the shell and Perl scripts that can migrate your name service data either
from source files or NIS maps to your Active Directory. These scripts are found in
/opt/ldapux/migrate/ads. The two shell scripts migrate_all_online.ads.sh and
migrate_all_nis_online.ads.sh migrate all your source files or NIS maps, while the Perl
scripts migrate_passwd_ads.pl, migrate_hosts_ads.pl, migrate_networks_ads.pl,
migrate_protocols_ads.pl, migrate_rpc_ads.pl, migrate_services_ads.pl,
migrate_group_ads.pl, and so forth, migrate individual maps. The shell scripts call the Perl
scripts.
The migration scripts require Perl, version 5 or later, which is installed with the NIS/LDAP
Gateway in /opt/ldapux/contrib/bin/perl.
Naming Context
The naming context specifies where in your directory your name service data will be, under the
base DN. For example, if your base DN is ou=unix, dc=cup, dc=hp, dc=com, the passwd
map would be at cn=people, ou=unix, dc=cup, dc=hp, dc=com. “Default Naming
Context” (page 256) shows the default naming context for the supported services. The default
will work in most cases.
Table C-14 Default Naming Context
Location in the Directory TreeMap Name
cn=Userspasswd
cn=Usersgroup
cn=Hostshosts
cn=Networksnetworks
cn=Protocolsprotocols
cn=Rcprpc
cn=Servicesservices
If you change the default naming context, modify the file migrate_common.ph and change it
to reflect your naming context.
NOTE: Since users and groups are migrated to the same container, they must have unique
names (common name) for the migration to succeed.
After the password and group data migration, the POSIX user accounts are disabled with no
password. This happens because UNIX user and group passwords cannot be migrated to Active
256 Command, Tool, Schema Extension Utility, and Migration Script Reference