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 ldapugmod Tool
The ldapugmod tool enables HP-UX administrators to modify existing POSIX accounts or groups
in an LDAP directory server. When using extended options, you can use ldapugmod to modify
arbitrary attributes for user or group entries or you can extend existing user or group entries
with the POSIX data model. To use ldapugmod, you must provide LDAP administrator credentials
that have sufficient privilege to perform the user or group modification operations in the LDAP
directory server.
Synopsis
ldapugmod [-t passwd] [options] [-h <hostname>] [-p <port>]
[-f <full_name>] [-n <new_name>] [-u <uid_number>] [-g <group/gid>]
[-s <login_shell] [-d <home_directory> [-m]] [-I <gecos>] [-c <comment>]
[[-A <attrval>][...]] [[-R <attrval>][...]] [-D <DN>|<uid_name>]
[[<attr>=<value>][...]]
ldapugmod -t group [options] [-h <hostname>] [-p <port>]
[-n new_name>] [-g <gid_number>] [-a <member>[,...]] [-r <member>[,...]]
[-c <comment>] [[-A <attrval>][...]][[-R <attrval>][...]]
[-D <DN>|<group_name>] [[<attr>=<value>][...]]
Options
The ldapugmod tool supports the following command options:
-P
Prompts for the administrator's bind identity (typically LDAP DN or Kerberos principal)
and bind password. If you do not specify the -P option, ldapugmod discovers the bind
identity and password from the environment variables LDAP_BINDDN and
LDAP_BINDCRED. If the LDAP_BINDDN and LDAP_BINDCRED environment variables
have not been specified, ldapugmod uses the bind configuration specified in the
LDAP-UX configuration profile. If the LDAP-UX configuration profile has specified the
“proxy” bind, ldapugmod reads the bind credential from either the
/etc/opt/ldapux/acred or the /etc/opt/ldapux/pcred file. The
/etc/opt/ldapux/acred file is only used by users who have sufficient administrative
privilege to read this file.
-PP
Prompts for the password of the user or group being modified. If you do not specify the
-PP option, the ldapugmod tool retrieves the password for the modified user or group
from the LDAP_UGCRED environment variable if the -PW option is specified. Use of -PP
implies the use of -PW.
-PW
Changes the user or group password attribute. If attribute mapping for the
userPassword attribute in the LDAP-UX configuration profile has not been defined
or set to *NULL*, ldapugmod will create new passwords in the userPassword attribute.
If you specify the -PW option, you must also specify either the LDAP_UGCRED environment
variable or the -PP option.
-O With ldapugmod, you can add posixAccount and posixGroup attributes to a user
or group entry that does not already contain the posixAccount or posixGroup object
class. This ability requires use of the -D option. With the -O option, ldapugmod attempts
to add the posixAccount or posixGroup objectclass and respective attributes
(depending on if the -t passwd or -t group option is specified) to the entry being
modified. When used with Microsoft Windows Active Directory service, if the user or
group entry is build using the abstract “User” or “Group” class, ldapugmod assumes
that the abstract class already includes the required Microsoft SFU attributes, and thus
does not add the posixAccount or posixGroup object class to the entry.
-Z
Requires an SSL connection to the LDAP directory server, even if the LDAP-UX
configuration profile does not specify the use of SSL. If you use the -Z option, you must
define either a valid directory server or CA certificate in the
/etc/opt/ldapux/cert8.db file. An error occurs if the SSL connection can not be
established.
202 Command, Tool, Schema Extension Utility, and Migration Script Reference