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
In this example, ldapcfinfo is used to access a Windows 2003 R2 Active Directory Server with
the R2's RFC 2307 schema installed. Assume that the homeDirectory attribute has been mapped
to unixHomeDirectory. The following command displays the attribute mapping for the
homeDirectory attribute.
./ldapcfinfo -t passwd -m homeDirectory
The output of the command is as follows:
homeDirectory=unixHomeDirectory
If ldapcfinfo is used to access a Windows 2000/2003 ADS with the SFU 3.0/3.5 schema installed,
the output of the command is as follows:
homeDirectory=msSFU30HomeDirectory
The following command displays the LDAP-UX default search base for the passwd name service.
In this example, “ou=users,” has been configured as the search base for the passwd name service.
./ldapcfinfo -t passwd -b
The output of the command is as follows:
ou=users,dc=org,dc=example,dc=com
The following command displays the LDAP-UX default search base for the group name service.
In this example, “ou=Groups,” has been configured as the search base for the group name service.
./ldapcfinfo -t group -b
The output of the command is as follows
ou=Groups,dc=org,dc=example,dc=com
The following command displays the location of the LDAP-UX configuration profile:
./ldapcfinfo -P
The output of the command is as follows:
dn: cn=ldapux-profile,dc=org,dc=example,dc=com
host: 55.5.22.15:389
If SSL is required to download the profile, the output of the command is as follows:
dn: cn=ldapux-profile,dc=org,dc=example,dc=com
hostssl: 55.5.22.15:636
The following command displays the required attributes defined in the default template file,
/etc/opt/ldapux/ug_templates/ug_passwd_ads.tmpl, when adding a new user account
to a Windows ADS:
./ldapcfinfo -t passwd -R
The following command displays the list of available template files for the passwd name service:
./ldapcfinfo -t passwd -L
Assume that /etc/opt/ldapux/ug_templates/ug_passwd_std.tmpl,
/etc/opt/ldapux/ug_templates/ug_passwd_default.tmpl
/etc/opt/ldapux/ug_templates/ug_passwd_ads.tmpl are currently available on the
system, the output of the above command is as follows:
LDAP User and Group Management Tools 223