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
Defining Directory Specific Information
Attribute type and object class definitions can be extended with directory-specific information
using the <dsSpecific> tag. This is useful to maintain a single schema definition file for
different types and versions of LDAP directory servers.
An Example of Defining Directory Specific Information in the Attribute Type Definition
This section takes an example to illustrate how directory specific information can be specified
in a single attribute type definition to support Netscape/Red Hat Directory Server and Windows
Active Directory Server specific definitions simultaneously.
The following is an example of the attribute type definition with directory specific information
using the <dsSpecific> tag:
Line 1: <attributeTypeDefinition>
Line 2: <oid>1.23.456.7.89101112.1.314.1.51.6<oid>
Line 3: <name>sampleAttribute</name>
Line 4: <displayName vendor="ads">
LINE 5: versionGreaterOrEqual="2003">my-sample-attribute</displayName>
LINE 6: <equlaity>caseIgnoreMatch</equality>
Line 7: <syntax>1.3.6.1.4.1.1466.115.121.1.15</syntax>
Line 8: <dsSpecific vendor="rhds" versionGreaterorEqual="6.2"
Line 9: versionLessThan="7.1"
Line 10: <field attr="X-ORIGIN">'Custom Schema'</field>
Line 11: </dsSpecific>
Line 12: <dsSpecific vendor="ads" versionLessThan="2003">
Line 13: <field attr="systemOnly">TRUE</field>
Line 14: <field attr="rangeLower">256</field>
Line 15: </dsSpecific>
Line 16: <dsSpecific vendor="ads" versionGreaterOrEqual="2003">
Line 17: <field attr="rangeLower">512</field>
Line 18: </dsSpecific>
Line 19: </attributeTypeDefinition>
For the above example, on Red Hat Directory Server 6.2 through 7.0, the X-ORIGIN flag for
sampleAttribute will be set to ‘Custom Schema’ as specified in the dsSpecific field. On
Red Hat Directory Server 6.1 and earlier, or 7.1 and later, the X-ORIGIN flag for
sampleAttribute will be set to the value specified in the <schemaSource>
On Active Directory Server 2000, the sampleAttribute is added using the same display name
as specified by the <name> value, with the rangeLower attribute set to 256, and the systemOnly
attribute set to TRUE.
On Active Directory Server 2003, the sampleAttribute is added using
“my-sample-attribute” display name, with the rangeLower attribute set to 512, and
the systemOnly attribute set to FALSE, which is the default value.
Table C-13 Directory Specific Information
ADS 2003ADS 2000RHDS 7.1RHDS 6.2–7.0Attribute
sampleAttributesampleAttributesampleAttributesampleAttribute
Name
my-sample-attributesampleAttribute
N/AN/ADisplay Name
N/AN/AAs Specified in
<schemaSource>
'Custom Schema'
X-ORIGIN
FALSE (default)TRUEN/AN/A
systemOnly
512256N/AN/A
rangeLower
Also, the 1.3.6.1.4.1.1466.115.121.1.15 syntax is not supported on the Windows ADS, it is mapped
to the corresponding Directory String syntax supported on Windows ADS, which is
attributeSyntax = 2.5.5.12, oMSyntax=64. See “Mapping Unsupported Matching Rules
and LDAP Syntaxes” (page 246) section for details.
242 Command, Tool, Schema Extension Utility, and Migration Script Reference