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
successfully mapped with a higher level (less specific) matching rule
supported by that server, <substitute matching rule name>, as
specified in the /etc/opt/ldapux/schema/map-rules.xml file. The
attribute types which uses this matching rule with the <substr>, <ordering>,
<equality> tags will use be queried or extended on the LDAP directory server
using <substitute matching rule name>].
LDAP Syntax Status Messages
SYNTAX_INVALID
LDAP syntax is missing a numeric oid. Edit the schema definition
file to specify one <oid> tag and its value for every
<syntaxDefiniton> definition.
[This message indicates the <oid> tag and its value need to be specified
in the <syntaxDefinition> definition in the
/etc/opt/ldapux/schema/schema-ds_type.xml file, where
ds_type corresponds to the same value specified with the -T option
on the command line when executing the ldapschema utility.]
SYNTAX_INVALID
LDAP syntax is missing an oMSyntax value. Edit the schema
definition file to specify one <oMSyntax> tag and its value for every
<syntaxDefiniton> definition.
[This message indicates the <oMSyntax> tag and its value need to be
specified in the <syntaxDefinition> definition in the
/etc/opt/ldapux/schema/schema-ds_type.xml file, where
ds_type corresponds to the same value specified with the -T option
on the command line when executing the ldapschema utility. The
<oMSyntax> tag is required for LDAP syntax definitions supported
by the Active Directory Server.]
SYNTAX_UNRESOLVED LDAP syntax "<syntax oid>” used in the “<attribute name>”
attribute type definition is not supported on the LDAP server. LDAP
syntax “<substitute syntax oid>” will be used instead
[This message indicates the specified syntax <syntax oid> is not
supported on the LDAP directory server. However, it was successfully
mapped with a higher level (more inclusive) syntax supported by
that server, <substitute syntax oid>, as specified in the
/etc/opt/ldapux/schema/map-rules.xml file. The attribute
types which uses this syntax with the <syntax> tag will use be queried
or extended on the LDAP directory server using the <substitute
syntax oid>.]
Extending schema containing invalid or incompatible attribute types or object classes is not
recommended. To install elements defined in a schema file containing invalid or incompatible
definitions requires specifying the force option (-F).
Schema Extension Utility 255