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
attribute mappings for the description attribute. If you do not
specify this option, the description attribute is not added to the
group entry.
-T <template_file>
Optional. Specifies the LDIF template file that is used to create new
group entries. If you do not specify the -T option, ldapugadd uses
the default template file either
/etc/opt/ldapux/ug_templates/ug_passwd_default.tmpl
or
/etc/opt/ldapux/ug_templates/ug_group_default.tmpl
depending on the service type you specify (-t passwd or -t
group).
The <template_file> parameter can be either a full or relative
path name or a short name. See “Template Files” (page 194) for
details.
<attr>=<value>
Optional. Enables specification of arbitrary LDAP attributes and
values. Because of potential object class requirements, additional
information beyond the basic POSIX account and group data may
need to be specified in order to create new entries in the LDAP
directory server. For example, if the person object class is used as
a structural class for posixAccounts, then the sn (surname) attribute
must be specified in order to properly create a new entry. This
attribute needs to be defined in the template file, and attribute/value
pair needs to be specified on the ldapugadd command line. The
<attr>=<value> parameter is used to specify attributes required
by the template file. However, if you specify an attribute that is not
defined in the defined template file, that attribute/value pair is
considered as an optional attribute/value and will be added to the
entry exactly as specified.
<attr>=<value> parameters are optional, but you must specify
them as the last parameters on the command line.
LDAP UG Tool Configuration File
LDAP-UX supports a local configuration file, /etc/opt/ldapux/ldapug.conf. The
ldapugadd tool uses the ldapug.conf file to manage the following default values when
creating new user and group entries in an LDAP directory server:
• A default group ID for new users.
• The valid UID number range for new users.
• The valid GID number range for new groups.
• The base path for a new user's home directory. By default, LDAP-UX appends the user's
account name to the base path to create the full path name.
• The default login shell for new users.
LDAP-UX provides the default ldapug.conf file as follows:
#
# This file is used by the ldapugadd tool for management
# of default values for creating new user and group entries.
# This file can not be modified directly, but instead through
# the ldapugadd -D command.
#
uidNumber_range=100:20000
gidNumber_range=100:2000
default_gidNumber=20
default_homeDirectory=/home
default_loginShell=/usr/bin/sh
LDAP User and Group Management Tools 193