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 following are limitations of ldapugadd:
• Because LDAP directory servers require data to be stored according to the UTF-8 (RFC3629)
character encoding method, all characters passed into ldapugadd are assumed to UTF-8,
and part of the ISO-10646 character set. ldapugadd does not perform conversion of the
locale character set to and from the UTF-8 character set.
• Because ldapugadd calls functions to discover if the group exists before adding a user to
a group, it is possible to encounter timing issues with cached information. For example, if
an administrator uses the grget command to see if a group exists, this group information
is cached by both ldapclientd (1M) and pwgrd(1M). If the group does not exist when
calling grget, and the administrator shortly creates this group with ldapugadd, the
information that the group still does not exist will still be cached. Then, when adding a new
user and specifying that this user is a member of the just created group, ldapugadd generates
an error to indicate that the user cannot be added to the group. To resolve this, you must
flush the pwgrd and ldapclientd caches.
Examples
This section provides examples of using the ldapugadd tool.
The following commands specify the LDAP_BINDDN and LDAP_BINDCRED environment variables:
export LDAP_BINDDN = "cn=Jane Admin,ou=admins,dc=org,dc=example,dc=com"
export LDAP_BINDCRED = "Jane's password"
The following command specifies the LDAP_URCRED environment variable. You must specify
the -PW option in the ldapugadd command line when using LDAP_UGCRED.
export LDAP_UGCRED = "user_password"
The following commands add an account entry for the user, alam, with the user's primary login
group id, 300. ldapugadd creates the password for new user, alam, using the user password
specified in the LDAP_UGCRED environment variable. After creating the user entry, ldapugadd
attempts to add this user as a member of the group member 300. The ldapugadd tool dynamically
assigns the uidNumber value from the pre-configured range.
cd /opt/ldapux/bin
./ldapugadd -t passwd -PW -f "Adrian Lam" -g 300 alam
Run the following command to display the new user entry, alam:
./ldapuglist -t passwd -n alam
Below is the user entry:
dn: cn=Adrian Lam,ou=users,dc=org,dc=example,dc=com
cn: Adrian Lam
uid: alam
uidNumber: 2200
gidNumber: 300
homeDirectory: /home/alam
loginShell: /usr/bin/ksh
The following command adds an account entry for the user, mscott, with the user's primary
login group id, 200, and gecos field information. In this example, the gecos attribute has been
mapped to cn, l and telephoneNumber in the LDAP-UX configuration profile. ldapugadd
creates the password for new user, mscott, using the password specified in the LDAP_UGCRED
environment variable. After creating the user entry, ldapugadd attempts to add this user as a
member of the group number 200.
./ldapugadd -t passwd -PW -g 200 -I "Mike Scott,Building-6A,555-555-5555" mscott
LDAP User and Group Management Tools 199