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
Example 4:
The remote LP printer, laser2, no longer supports LPD printing protocol. IPP printing protocol
is implemented instead. The administrator updated the printer object by changing the printing
protocol to IPP. The following shows the updated printer objects in the directory server:
dn: printer-name=laser2,ou=printers,dc=hp,dc=com
printerbyname: laser2
printer-resource: ipp://hostC.hp.com/lj2004
printer-location: Engineering Lab
printer-model: Hewlett Packard laserjet Model 2004N
printer-service-person: David Lott
IPP printing protocol is not supported by the LP spool printing system. The only action that the
LDAP printer configurator will take is to remove the current laser2 printer configuration on
the client system.
Example 5:
The administrator created a new printer object in the directory server as below:
dn: printer-name=laser8,ou=printers,dc=hp,dc=com
printerbyname: laser8
printer-resource: lpd://hostD.hp.com/lj81003
In this example, the printer configurator adds a new remote LP laser8 printer configuration
to the client system.
However, if the user attempts to remove the laser8 printer configuration manually, the printer
configuration will no longer be managed by the printer configurator. The user has to recreate
the printer configuration manually in case the laser8 printer is needed. The printer configurator
does not try to create the printer configuration even though the printer object of laser8 still
exists in the directory server.
If the user manually adds a remote LP printer configuration to the client system, the new printer
configuration will not be managed by the printer configurator. The user has to remove the printer
configuration manually if the remote LP printer is no longer needed.
Limitations of Printer Configurator
• LDAP-UX Client Services only suports the HP-UX LP spooler system, network printers, and
printerservers that support Line Printer Daemon (LPD) protocol. The printer configurator
does not support local printers.
• In a global management envoriment, it is hard to determine a default printer for the individual
client system. The LDAP printer configurator treats every printer entry as the regular printer.
The administrator or user requires to manually select a printer as a default printer for the
client system.
NOTE: The LDAP Printer Configurator will only add or remove printers that it has discovered
in the LDAP directory according to the search filter that defined for the printer services.
Limitations of Printer Configurator 79