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
This command adds an instance of the cn attribute, cn=Joesh Scott to the entry. The result
of the user entry is as follows:
dn: uid=jscott,ou=users,dc=org,dc=example,dc=com
cn: John Scott
cn: Joe Scott
cn: Joesh Scott
uid: jscott
uidNumber: 2500
gidNumber: 120
homeDirectory: /home/jscott
loginShell: /usr/bin/sh
gecos: John Scott,San Jose,+1 505-555-5000
Specific Return Codes for ldapugmod
The ldapugmod tool returns a list of return codes shown in Table C-8.
Table C-8 Return Codes for ldapugmod
MessageReturn Code
Cannot discover user's home directory information.
MOD_CANNOT_GET_USER_HOMEDIR
Member(s) need to be specified for the specified option.
For exmaple,
ldapugmod -t group -r ""
The output of the command is as follows:
ERROR: MOD_COMMANDLINE_ERR:
member(s) need to be specified for -r
option.
ldapugmod -t group -a ""
The output of the command is as follows:
ERROR: MOD_COMMANDLINE_ERR:
member(s) need to be specified for -a
option.
MOD_COMMANDLINE_ERR
Cannot remove user account from the specified group,
will be skipped.
MOD_MEMBER_SKIPPED
Duplicate modification requests are found in the
command options. For example,
ldapugmod -A "cn=Mike Lee" -A "cn=Mike Lee”
mlee
After running the above command, ldapugmod exits
with the MOD_DUP_REQUEST error status because
duplicate modification requests are specified.
MOD_DUP_REQUEST
Conflict modification requests are found in the command
options.
MOD_CONFLICT_REQUEST
Rename entry's RDN failed.
MOD_RENAME_RDN_FAILED
The specified command deletes the existing value in the
RDN, but no new value for the RDN has been provided.
MOD_NEW_RDN_NEEDED
The account entry being added is already a member of
the specified group.
MOD_MEMBER_EXIST
The user's home directory does not exist.
MOD_HOMEDIR_DOESNOT_EXIST
Cannot move user's home directory, missing information.
MOD_MISSING_INFORMATION
210 Command, Tool, Schema Extension Utility, and Migration Script Reference