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
Object Class Definition Requirements
To add the new schema to the LDAP directory server, each object class definition must meet the
following requirements:
• The object class definition contains a <oid> tag with one numeric id value which adheres
to RFC 2252 format specification.
• The object class definition has at least one <name> tag with the object class name. Each name
must adhere to RFC 2252 format specification.
• No other object classes in the schema definition file or on the LDAP directory server have
the same numeric id value.
• No other object classes in the schema definition file or on the LDAP directory server have
the same name value.
• The super-class(es) used by the object class must be defined.
• The attribute(s) used by the object classes must be defined.
• The inheritance hierarchy has no cycles (no circular dependencies exist in the super-class
and sub-class relationships).
• An ABSTRACT object class can specify only ABSTRACT object class(es) as its super-class(es).
• An AUXILIARY object class can specify ABSTRACT or AUXILIARY object class(es) as its
super-class(es).
• A STRUCTURAL object class can specify ABSTRACT or STRUCTURAL object class(es) as its
super-class(es).
Predefined Schema Definition Files
The following LDAP schema definition files are delivered with the LDAP-UX product:
• /etc/opt/ldapux/schema/rfc2256.xml
• /etc/opt/ldapux/schema/rfc2307.xml
• /etc/opt/ldapux/schema/rfc2307–bis.xml
• /etc/opt/ldapux/schema/rfc2926.xml
• /etc/opt/ldapux/schema/rfc3712.xml
These files are provided as examples to demonstrate how to define new LDAP schema definition
files to use with the ldapschema utility. Since these files define attribute types and object classes
that come pre-installed on most LDAP directory servers they are not intended for extending the
LDAP directory server schema. Instead, these files are provided for reference when creating the
new schema definition files to query and extend the LDAP directory server schema with the new
attribute type and object class definitions.
Schema Extension Utility 241