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
An Example of Defining Directory Specific Information in the Object Class Definition
Directory specific information can be specified in the object class definitions as well as in optional
and mandatory attributes.
The following is an example of the object class definition with directory specific information
using the <dsSpecific> tag and XML attributes, not and only:
Line 1: <objectClassDefinition>
Line 2: <oid>1.23.456.7.89101112.1.314.1.51.7<oid>
Line 3: <name>sampleObject</name>
Line 4: <must only="ads">serverRole</must>
Line 5: <must not="ads">userPassword</must>
Line 6: <may>sampleAttribute</may>
Line 7: <dsSpecific vendor="ads">
Line 8: <field attr="systemOnly">TRUE</field>
Line 9 </dsSpecific>
Line 10: </objectClassDefinition>
For the above example, on Windows Active Directory Server, this object class has a mandatory
attribute type, serverRole, and an optional attribute type, sampleAttribute. On all other
types of directory servers, this object class has a mandatory attribute type, userPassword and
an optional attribute, sampleAttribute. On Windows Active Directory Server, this object class
has the systemOnly attribute set to TRUE.
NOTE: Directory-specific attributes and values specified in <dsSpecific> fields are not
validated. You need to ensure that the values specified in these fields are legitimate and adhere
to the LDAP directory server rules. The field value must be specified exactly as it is to appear in
the attribute type or object class definition, using single and double quotes as applicable.
Attributes and values specified in the <dsSpecific> fields override the default attribute type
and object class configurations. For example, on Windows Active Directory Server the default
value of the isDefunct attribute is set to False. If the following <dsSpecific> attribute is
defined, the specific setting will override the default setting and will result in the element being
defunct.
<dsSpecific vendor="ads">
<field attr="isDefunct">TRUE</field>
</dsSpecific>
Schema Extension Utility 243