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
NOTE: You must copy the file my_profile.bin
to/etc/opt/ldapux/ldapux_profile.bin to activate the profile.
create_profile_schema
This tool, found in /opt/ldapux/config, extends the Active Directory schema with the
DUAConfigProfile object class using the information you provide interactively. Typically you
run the setup program instead of running this program directly.
Syntax
create_profile_schema
display_profile_cache
This tool, found in /opt/ldapux/config, displays information from a binary profile (cache)
file. By default, it displays the currently active profile in
/etc/opt/ldapux/ldapux_profile.bin.
Syntax
display_profile_cache [-i infile] [-o outfile]
where infile is a binary profile file, /etc/opt/ldapux/ldapux_profile.bin by default,
and outfile is the output file, stdout by default.
The binary profile contains mappings for all backend commands (even those that are unused or
unsupported by LDAP-UX Client Services with Active Directory); all of which are displayed by
display_profile_cache. The actual client configuration can be reviewed in the configuration
profile LDIF file /etc/opt/ldapux/ldapux_profile.ldif.
Examples
The following command displays the profile in the binary profile file
/etc/opt/ldapux/ldapux_profile.bin to stdout:
display_profile_cache
The following command displays the profile in the binary profile file my_profile.bin and
writes the output to the file profile:
display_profile_cache -i my_profile.bin -o profile
get_profile_entry
This tool, found in /opt/ldapux/config downloads a profile from an LDAP directory into
an LDIF file and calls create_profile_cache to create a binary profile file, thereby activating
it on the client. This tool looks in the local client configuration file
/etc/opt/ldapux/ldapux_client.conf for the profile DN.
Syntax
get_profile_entry -s service [-o outfile]
[-D bindDN -w passwd] [-p profile_id]
where service is the name of a supported service, typically NSS, outfile is the name of a file
to contain the LDIF output, by default /etc/opt/ldapux_profile.ldif, and profile_id
is <remote domain name> or gc for PROFILE_ID field in
/etc/opt/ldapux/ldapux_client.conf. The -p option only applies if you want to configure
multiple domains.
168 Command, Tool, Schema Extension Utility, and Migration Script Reference