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
dn: cn=GroupC,ou=Groups,dc=org,dc=example,dc=com
cn: GroupC
gidNumber: 500
MemberUid: alouie
Description: A IT Group
Description: A Group Entry
Run the following command to add an instance of the description attribute and value to the
group entry, GroupC, without removing already existing values for that attributes:
./ldapugmod -t group -A "description=Group C Entry" groupC
The result of the GroupC entry is as follows:
dn: cn=GroupC,ou=Groups,dc=org,dc=example,dc=com
cn: GroupC
gidNumber: 500
MemberUid: alouie
Description: A IT Group
Description: A Group Entry
Description: Group C Entry
The following command adds the three members, atam, mlou, mscott, to the group entry,
groupA:
./ldapugmod -t group -a atam,mlou,mscott GroupA
The following command removes one member, atam from the group entry, groupA:
./ldapugmod -t group -r atam GroupA
Command Arguments
The following describes arguments/options used in the previous examples for the ldapugmod
-t group commands:
-A <attrval>
Specifies an attribute and value to be added to an entry. When
working with multi-valued attributes, you can use the -A option to
add a new value for a multi-valued attribute, without removing
already existing values for that attributes.
-g <gidNumber>
Replaces the group's numeric id number.
-a <member>[,...]
Adds one or more members to the specified group. When specifying
a list of members, you must use a comma with no white space to
separate each member.
-r <member>[,...]
Removes one or more members from the specified group. When you
specify a list of members, you must use a comma with no white space
to separate each member.
Deleting a User or a Group
You can use ldapugdel to remove POSIX user and group entries from an LDAP directory
server. With the -O option, ldapugdel enables you to remove only POSIX related attributes
and object classes from a user or group entry without removing the entire entry.
The userPassword, uid, cn and description attributes are commonly used by most other
user and group schemas. With the -O option, the ldapugdel tool does not attempt to remove
these attributes. The uidNumber, gidNUmber, loginShell, homeDirectory, gecos and
memberUid are more unique to the POSIX schema, and are removed when the -O option is
specified.
User and Group Management 135