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
-j <filename>
Specifies an administrator’s password in the file (for simple authentication).
-w-
Inputs an administrator’s password from the prompt (for simple
authentication).
-Z
Establishes an SSL-encrypted connection.
-ZZ
Specifies TLS request.
-ZZZ
Enforces TLS request (requires successful server response).
-P path
Specifies path to SSL certificate database. (Default: /etc/opt/ldapux)
-3
Verifies the host name in SSL certificates.
-s-
Disables syntax substitution in attribute types. Normally, if an attribute
type uses an LDAP syntax not supported on the LDAP directory server, it
is mapped to use a higher level (more inclusive) syntax supported by that
server. If this option is specified, any attribute types that use unsupported
LDAP syntax will not be added to the LDAP directory server schema. See
“Mapping Unsupported Matching Rules and LDAP Syntaxes” (page 246)
section for more details.
-m-
Disables matching rule substitution in attribute types. Normally, if an
attribute type uses a matching rule not supported on the LDAP directory
server, it is mapped to use a higher level (less specific) matching rule
supported by that server. If this option is specified, any attribute types that
use unsupported matching rules will not be added to the LDAP directory
server schema. See the “Mapping Unsupported Matching Rules and LDAP
Syntaxes” (page 246) section for more details.
-f <filename>
Store schema extension instructions in the specified file. File format depends
on the vendor and version of the LDAP directory server (usually LDIF).
When this option is specified, ldapschema will not apply any changes to
the LDAP directory server or its schema. This option requires specifying
“–e” option. If <filename> is set to “–“ (–f –), the output is redirected to
standard output, otherwise it is stored in the specified <filename>.
-F
Forces installation of schema even if it contains any invalid attribute type
or object class definitions, or some components specified in the schema file
are already present in the LDAP directory server.
-v
Display verbose information to standard output.
234 Command, Tool, Schema Extension Utility, and Migration Script Reference