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
Mapping Unsupported Matching Rules and LDAP Syntaxes
If matching rules and/or LDAP syntaxes used in attribute type definitions in the schema definition
file are not supported on the LDAP directory server, the ldapschema tool maps them to alternate
matching rules and syntaxes the LDAP server supports. LDAP-UX provides the
/etc/opt/ldapux/schema/map-rules.xml file which defines a list of default substitution
matching rules and syntaxes, and alternate matching rules and syntaxes.
The matching rules are specified in <equality>, <ordering> or <substr> in the attribute
type definition. The LDAP syntax is specified in the <syntax> tag of the attribute type definition.
The purpose of the mapping rules file is to allow an LDAP schema to be installed on an LDAP
directory server even if some of matching rules and LDAP syntaxes used in the definition of that
schema are not supported by the directory server. The
/etc/opt/ldapux/schema/map-rules.xml file uses the following mapping rules guideline:
• Map more restrictive syntaxes to less restrictive syntaxes.
• Map more specific matching rules to less specific matching rules.
For example, the Integer syntax contains a subset of characters of the IA5 string syntax. Therefore,
it is acceptable to map the Integer syntax to the IA5 string syntax, since the IA5 string syntax is
a super-set of the integer syntax.
Examples of Alternate Matching Rules and Syntaxes in /etc/opt/ldapux/map-rules.xml
The following shows examples of alternate matching rules and syntaxes defined in the
/etc/opt/ldapux/map-rules.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mappingPolicies SYSTEM "/etc/opt/ldapux/schema/schema.dtd">
<mappingPolicies>
<defaultMatchingRulesReplacements>
<defaultMatchingRule>
<matchingRule>caseIgnoreMatch</matchingRule>
</defaultMatchingRule>
</defaultMatchingRulesReplacements>
<defaultSyntaxesReplacements>
<defaultSyntax only="ads">
<syntax>2.5.5.12</syntax>
<desc>Active Directory String syntax.</desc>
<oMSyntax>64</oMSyntax>
</defaultSyntax>
<defaultSyntax not="ads">
<syntax>1.3.6.1.4.1.1466.115.121.1.15</syntax>
<desc>Directory String syntax.</desc>
</defaultSyntax>
</defaultSyntaxesReplacements>
<matchingRulesReplacements>
<matchingRules>
<matchingRule>IntegerMatch</matchingRule>
<subRule>
<matchingRule>numericStringMatch</matchingRule>
</subRule>
</matchingRules>
</matchingRulesReplacements>
<syntaxesReplacements>
<syntaxes>
<syntax>1.3.6.1.4.1.1466.115.121.1.26</syntax>
<desc> IA5 String Syntax.</desc>
<equivSyntax>
<syntax>2.5.5.5</syntax>
<desc>Active Directory IA5 String LDAP Syntax.</desc>
246 Command, Tool, Schema Extension Utility, and Migration Script Reference