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
Limitations
The ldapuglist tool has the following limitations:
• The ldapuglist tool does not support enumeration of members of a dynamic group, such
as those defined by the dynamic group attributes, memberURL or msDS-AzLDAPQuery.
• The ldapuglist tool does not perform conversion of the locale character set to and from
the UTF-8 character set.
Examples
This section provides examples of using ldapuglist.
While use of LDAP_BINDDN is not typically required to use ldapuglist, the LDAP_BINDDN
and LDAP_BINDCRED environment variables can be used to specify the Distinguished Name
(DN) and password of a user with sufficient directory server privilege to display protected
attributes.
Setting the LDAP_BINDDN and LDAP_BINDCRED environment variables is optional when using
ldapuglist. The following commands set these two environment variables:
export LDAP_BINDDN = "cn=Jane Admin,ou=admins,dc=org,dc=example,dc=com"
export LDAP_BINDDN = "Jane's password"
Run the following command to go to the /opt/ldapux/bin directory where ldapuglist
resides:
cd /opt/ldapux/bin
Run the following command to display the account entry for the user name, ascott:
./ldapuglist -t passwd -L -n ascott
The output of the above command displays the /etc/passwd format as follows:
ascott:x:125:250:ascott:/home/ascott:/usr/bin/sh
Run the following command to list an account entry that contains uid=mlee:
./ldapuglist -t passwd -f "(uid=mlee)"
The output is as follows:
dn: cn=Michael Lee,ou=users,dc=org,dc=example,dc=com
cn: Michael Lee
uid: mlee
uidNumber: 2201
gidNumber: 318
homeDirectory: /home/mlee
loginShell: /usr/bin/ksh
gecos: mlee,San Francisco,555-555-5555
Run the following command to list an account entry that contains uid=jscott:
./ldapuglist -t passwd -m -f "(uid=jscott)"
In this example, ldapuglist is used to access a Windows 2003 R2 Active Directory Server with
the R2's RFC 2307 schema installed. The homeDirectory attribute has been mapped to
unixHomeDirectory and the gecos attribute has been mapped to cn, l, and
telephoneNumber. With the -m option, the ldapuglist tool displays the entry with the
mapped attribute names as follows:
dn: cn=John Scott,ou=users,dc=org,dc=example,dc=com
cn[cn]: John Scott
uid[uid]: jscott
182 Command, Tool, Schema Extension Utility, and Migration Script Reference