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
Use the following command to display the new user entry, mscott, with mapped attribute
information:
./ldapuglist -t passwd -m -n mscott
If ldapugadd is used to access a Windows 2003 R2 Active Directory Server with the R2's RFC
2307 schema installed, the output of the user entry is as follows:
dn: cn=Mike Scott,ou=users,dc=org,dc=example,dc=com
cn[cn]: Mike Scott
uid[uid]: mscott
uidNumber[uidnumber]: 2200
gidNumber[gidnumber]: 200
homeDirectory[unixHomeDirectory]: /home/mscott
loginShell[loginshell]: /usr/bin/sh
gecos[cn]: Mike Scott
gecos[l]: Building-6A
gecos[telephoneNumber]: 555-555-5555
If ldapugadd is used to access a Windows 2000/2003 Active Directory Server with the SFU
3.0/3.5 schema installed, the output of the user entry is as follows:
dn: cn=Mike Scott,ou=users,dc=org,dc=example,dc=com
cn[cn]: Mike Scott
uid[msSFU30uid]: mscott
uidNumber[msSFU30uidnumber]: 2200
gidNumber[msSFU30gidnumber]: 200
homeDirectory[msSFU30HomeDirectory]: /home/mscott
loginShell[msSFU30loginshell]: /usr/bin/sh
gecos[cn]: Mike Scott
gecos[l]: Building-6A
gecos[telephoneNumber]: 555-555-5555
The following command adds an account entry for the user, mwang, with the user's primary
login group id, 350. In this example, ldapugadd creates the user home directory /home/wang
and assigns user and group ownership of the newly created directory to the user mwang and his
primary login group after successfully adding the user entry to the directory server and adding
the user to the primary login group. ldapugadd uses the password specified in the LDAP_UGCRED
environment variable to create the password for the new user, mwang.
./ldapugadd -t passwd -PW -f "Mike Wang" -g 350 -m -d "/home/wang" mwang
Use the following command to display the new user entry, mwang:
./ldapuglist -t passwd -n mwang
The output of the user entry is as follows:
dn: cn=Mike Wang,ou=users,dc=org,dc=example,dc=com
cn: Mike Wang
uid: mwang
uidNumber: 2255
gidNumber: 350
homeDirectory: /home/wang
loginShell: /usr/bin/sh
The following command adds a new group entry for the group name, groupA. In this example,
ldapugadd creates the new group, groupA, and defines the initial group membership by adding
the user account, mwang, as a member.
./ldapugadd -t group -M mwang groupA
200 Command, Tool, Schema Extension Utility, and Migration Script Reference