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
<oMSyntax>22</oMSyntax>
</equivSyntax>
<subSyntax>
<syntax>1.3.6.1.4.1.1466.115.121.1.15</syntax>
<desc>Directory String syntax.</desc>
</subSyntax>
</syntaxes>
</syntaxesReplacements>
</mappingPolicies>
How Does ldapschema Map Unsupported Matching Rules and LDAP Syntaxes
If any mapping rules or the syntax used by an attribute type are not supported on the LDAP
server, the ldapschema utility checks if the appropriate substitution rule is specified in the
/etc/opt/ldapux/map-rules.xml file. If it is specified, ldapschema locates the first
available matching rule or syntax supported on the LDAP server, and uses it in the attribute type
definition instead. If the substitution rule is not specified, or none of the substitution matching
rules or syntaxes are supported on the LDAP directory server, ldapschema checks if the default
substitution can be used.
The “vendor”, “versionGreaterOrEqual” and “versionLessThan” XML attributes can
be used to specify directory-specific information stored in <defaultMatchingRule> and
<defaultSyntax> tags. If the default substitution is not supported on the LDAP server, the
attribute type cannot be added to the LDAP directory server schema.
Examples
For example, an attribute type with IA5String syntax (1.3.6.1.4.1.1466.115.121.1.26)
is installed on Windows ADS, where this IA5 String syntax is not supported. ldapschema will
try using the first specified equivalent or substitution syntax supported by the target LDAP
directory server. The specified equivalent syntax of 2.5.5.5 syntax with the oMSyntax value
of 22 is supported on windows ADS and will be used in place of the original syntax value.
As another example, assume an attribute type with a Boolean equality rule is being installed on
the LDAP server where this matching rule is not supported. Since no substitution policy is
specified for this matching rule in the example above, the default substitution matching rule,
caseIgnoreMatch, would be used instead, if the LDAP server supports it. If the LDAP server
does not support caseIgnoreMatch, that attribute type cannot be installed on the LDAP server,
unless its definition is modified to use another supported equality matching rule.
If the –s– option is specified in the ldapsechema tool, syntax substitution in attribute types is
disabled. Any attribute types with unsupported LDAP syntaxes will not be added to the LDAP
directory server schema. The –m– option with the ldapschema tool disables matching rule
substitution. Any attribute types with unsupported matching rules will not be added to the
LDAP directory server schema.
Schema Extension Utility 247