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 Status Messages
OBJECT_INVALID
Object class definition is missing a numeric oid. Edit the schema
definition file to specify one <oid> tag and its value for every
<objectClassDefiniton> definition.
[This message indicates the <oid> tag and its value need to be specified
in the <objectClassDefinition> definition in the <schema> file.]
OBJECT_INVALID
Object Class definition is missing a name. Edit the schema definition
file to specify at least one <name> tag and its value for every
<ObjectClassDefiniton> definition.
[This message indicates the <name> tag and its value need to be
specified in the <objectClassDefinition> definition in the
<schema> file.]
OBJECT_INVALID Object class “<object name>” has an invalid object type value. Edit
the schema definition file to modify the value specified with the
<type> tag, which can be one of the following:
• STRUCTURAL
• AUXILIARY
• ABSTRACT
[This message indicates the <type> tag value needs to be corrected
in the<objectClassDefinition> definition in the <schema> file.
Possible object class type values are STRUCTURAL, AUXILIARY or
ABSTRACT. Any other type values are rejected. If the <type> tag is
not specified in the <objectClassDefinition> definition, the
default object class type value is STRUCTURAL. See RFC 2252 for
details.]
OBJECT_UNRESOLVED Super-class used in "<object name>” object class definition is not
defined in any LDAP schema.
[This message indicates the super-class specified with the
<subClassOf> tag in the given object class definition is undefined.
Edit the <schema> file to correct the name of the super-class in the
object class definition. The super-class used in the object class
definition must be defined either in the LDAP directory server schema
or in the <schema> file before this object class can be installed.]
OBJECT_UNRESOLVED Mandatory attribute used in the <object name> object class
definition is not defined in any LDAP server schema.
[This message indicates the mandatory attribute type specified with
the <must> tag in the given object class definition is undefined. Edit
the <schema> file to correct the name of the mandatory attribute in
the object class definition. The mandatory attribute used in the object
class definition must be defined either in the LDAP directory server
schema or in the <schema> file before this object class can be installed.]
OBJECT_UNRESOLVED Optional attribute used in “<object name>” object class definition
is not defined in any LDAP server schema.
[This message indicates the mandatory attribute type specified with
the <may> tag in the given object class definition is undefined. Edit
the <schema> file to correct the name of the optional attribute in the
object class definition. The optional attribute used in the object class
definition must be defined either in the LDAP directory server schema
or in the <schema> file before this object class can be installed.]
Schema Extension Utility 253