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

Directory Server Security Policies
Global Security Attributes
In the Windows 2003 Active Directory Server, there are a number of attributes about the security
policies. In order to support account and password security policy enforcement, PAM_AUTHZ
is enhanced to support the global administrative security attributes listed in table 7–2.
They are used to define the policy rules and are all defined under dc=world,dc=hp,dc=com.
Only authorized users can access them. If you use the PAM_Authz enhancement to support the
account and password policy enforcement, you must configure LDAP-UX with a proxy user and
grant this proxy user read and search rights to search dc=world, dc=hp, dc=com.
Table 7-2 Global Security Attributes
DescriptionAttribute
This integer attribute defines the amount of time that an account is locked due
to the Lockout-Threshold being exceeded. This value is stored as a large integer
that represents the negative of the number of 100 nanosecond intervals from
the time the Lockout-Threshold is exceeded that must elapse before the account
is unlocked.
lockoutDuration
This integer attribute specifies the maximum amount of time a password is
valid. This value is stored as a large integer that represents the number of 100
nanosecond intervals from the time the password was set before the password
expires.
maxPwdAge
Security Policy Status Attributes
PAM_AUTHZ supports a list of attributes which hold the general security policy status
information for a particular user in the Netscape/Red Hat Directory Server shown as table 7–3.
Table 7-3 Security Policy Status Attributes
DescriptionAttribute
This attribute controls the behavior of the user account.
userAccountControl
This string attribute contains the NetBIOS or DNS names
of the computers running Windows NT Workstation or
Windows 2000 Professional from which the user can log
on. Each NetBIOS name is separated by a comma.
userWorkStations
This integer attribute defines the date and time that the
password for this account was last changed. This value
is stored as a large integer that represents the number of
100 nanosecond intervals since January 1, 1601 (UTC). If
this value is set to 0 and the userAccountControl
attribute does not contain the UF_DONT_EXPIRE_PASSWD
flag, then the user must set the password at the next logon.
pwdLastSet
This integer attribute specifies the time when the account
expires. This value represents the number of 100
nanosecond intervals since January 1, 1601 (UTC). A value
of 0 or 0x7FFFFFFFFFFFFFFF (9223372036854775807)
indicates that the account never expires.
accountExpires
This integer attribute specifies the date and time (UTC)
that this account was locked out. This value is stored as
a large integer that represents the number of 100
nanosecond intervals since January 1, 1601 (UTC). A value
of zero means that the account is not currently locked out.
lockoutTime
This integer attribute defines the number of hours that
the user is allowed to logon to the domain.
logonHours
PAM_AUTHZ Login Authorization 121