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
The ldapuglist Tool
You can use the ldapuglist tool to display and enumerate POSIX-like account and group
entries stored in an LDAP directory server, without requiring extensive knowledge of the methods
used to retrieve and evaluate that information in the LDAP directory server.
The ldapuglist tool uses the LDAP-UX profile configuration, requiring minimal command
line options to discover where to search for user or group information, such as the LDAP directory
server host and proper search filters for finding users and groups. This tool provides command
options that enable you to alter these configuration parameters.
The ldapuglist tool supports the followings:
• ldapuglist uses the existing LDAP-UX authentication configuration to determine how
to bind to the LDAP directory server.
• ldapuglist performs attribute value translation to POSIX-like syntaxes. For example, if group
membership is defined using X.500-style DN strings, ldapuglist will convert those strings
to simple member ids.
• ldapuglist supports attribute mappings as specified in the LDAP-UX configuration
profile. The mapped attributes and values can be displayed. The output format of
ldapuglist is similar to an LDIF format (RFC 2849). It is not LDIF. Major differences
include:
— ldapuglist does not display object classes.
— By default, ldapuglist only displays POSIX-related attributes, unless you specifically
request an attribute list with the <attr> option on the command line.
— Output lines are not broken after 80 columns.
Synopsis
ldapuglist [options] [-t <type>] [-h <hostname>] [-p <port>] [-n <name>]
[-f|F <filter>] [-b <base>] [-s <scope> [-N <maxcount>] [<attr>...]
Options
The ldapuglist tool supports the following command options:
-m Displays the names of the mapped attributes when returning results. Without the -m
option, ldapuglist displays results as follows:
fieldname: value
Where fieldname is one of the predefined RFC 2307 attribute names, and value is the
value for that field.
With the -m option, the ldapuglist tool displays the actual attribute mapping name
as follows:
fieldname[mapped attributename]: value
In the following example, if the RFC 2307 attribute gecos has been mapped to the cn,
l (location) and telephoneNumber attributes. Without the -m option, the output of
the gecos field is:
gecos: Bill Wan,Building 45,1-555-555-5431
When the -m option is specified, the output representing the gecos field is as follows:
gecos[cn]: Bill Wang
gecos[l]: Building 45
gecos[telephoneNumber]: 1-555-555-5431
When a field has been mapped to multiple attributes, those attributes will appear in the
order as defined in the LDAP-UX configuration profile.
LDAP User and Group Management Tools 175