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

The ldapcfinfo Tool
Use the ldapcfinfo tool to discover LDAP-UX configuration information about the LDAP-UX
product. The ldapcfinfo tool can also be used to discover the list of required attributes when
creating new users or groups to an LDAP directory server. Non-interactive LDAP applications
can use this tool to find LDAP-UX configuration details when adding new users or groups. The
ldapcfinfo tool can also report if LDAP-UX is properly configured and active for the specified
service.
Synopsis
ldapcfinfo [-t <type>] [-T <template_file>] [-a <DN>] [-m <atobName>]
[-A|-P|-D|-L |-R|-b|-s |-f |-h]
Options
NOTE: Because each of the -a, -D, -A, -P, -R, -L, -b, -f, -h and -m options described below
generates arbitrary output formats, you may only use one of these options per invocation of the
ldapcfinfo command. Use of multiple of these options in a single command line may prevent
you from distinguishing outputs applied to a specific option, and will result in an error. The -T
option is ignored unless the -R option is specified.
The ldapcfinfo tool supports the following command options:
-t <type>
Specifies the type of the service name for which to retrieve
configuration information. The valid service names are passwd,
group, netgroup, services, rpc, hosts, networks,
automount, automountmap, publickey, protocols and pam.
If you do not specify this argument, ldapcfinfo defaults to the
passwd name service (if applicable to the argument specified). If
the -t option is the only argument specified on the command line,
ldapcfinfo reports if LDAP-UX is properly configured and active
for the specified service.
-A Reports if the user running the ldapcfinfo command has the
ability to access the LDAP administrator’s credential, if configured.
ldapcfinfo returns zero exit status if the user has rights to access
the LDAP administrator’s credential. The ldapcfinfo tool returns
a non-zero exit status if the user does not have permission. For
detailed information about the LDAP-UX administrator credential,
see the section titled “Configure LDAP-UX Client Services with
Publickey Support” in the LDAP-UX Client Services Administrator's
Guide available at:
http://docs.hp.com/en/internet.html
-P
Displays the distinguished name (DN) of the LDAP-UX
configuration profile and LDAP directory server that stores that
profile. The output format is as follows:
dn: distinguishedName
host: hostname/ip:port
If SSL or TLS is configured to download the profile, host: is
replaced with hostssl:.
-R
Displays the required attributes as defined in the default template
file or the template file specified with the -T option. If you do not
specify the -T option, you must specify the -t passwd or -t
group option to indicate which default template file to be examined.
Each attribute required by the requested template file displays on
LDAP User and Group Management Tools 219