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
Step 3: Setting Read Permissions for the Proxy User
The LDAP query groups (dynamic groups) created by Authorization Manager are not placed
under the CN=Users container. Authorization Manager creates its own authorization store
objects (for example, CN=dyngroup). By default, a regular user is not allowed to read LDAP
entries under those authorization store objects.
To support dynamic group feature with LDAP-UX, you must configure the proxy user to grant
the read permissions for those authorization store objects. Use the ADSI edit and execute following
procedures to grant the proxy user read permissions for a sample authorization store object,
CN=dyngroup, containing dynamic groups:
1. Start mmc from run to bring up console.
2. Add snap-in ADSI edit .
3. Connect to domain from Action.
4. Select the authorization store object, CN=dyngroup, and right-click on the properties
tab.
5. Click on the Security tab on the properties window.
6. Click on Add button on the Security window.
7. Add the proxy user and click on OK button.
8. On the permissions dialog box, select the Allow box for the read permission.
9. Click on the Advanced button on the Security window.
10. Select proxy user and click on the Edit button.
11. Choose the This object and all child objects selection from Apply onto drop
down list in the dialog box.
12. On the permissions dialog box, verify that the List Contents, Read All Properties
and Read Permissions selections are checked.
To support dynamic groups with LDAP-UX, you must configure the proxy user to grant the
read permissions for each authorization store object in Windows ADS. If you configure dynamic
groups more than one domain, the above procedures must be performed to every domain that
you want to support with LDAP-UX.
Multiple Group Attribute Mappings
LDAP-UX supports the dynamic group attribute, msDS-AzLDAPQuery, for Windows 2003 or
2003 R2 ADS.
By default, LDAP-UX uses the memberUid attribute to retrieve group members. With the support
of X.500 group member syntax, you can map the default group attribute, memberUid, to member
which you specify group members using user DNs. If you use Authorization Manager to create
dynamic groups for Windows 2003 or 2003 R2 ADS, LDAP-UX allows you to map memberUid
to msDS-AzLDAPQuery .
You can run the setup tool and map memberUid to multiple attributes as needed. For example,
the following output of /opt/ldapux/config/display_profile_cache shows that
memberUid is mapped to both static group attributes, memberUid and member, and the dynamic
group attribute, msDS-AzLDAPQuery (assuming that the LDAP directory server is Windows
2003 R2 ADS):
Group Service Configuration:
Attribute: is mapped to:
----------- -------------
name: cn
gid: gidnumber
members: memberuid msDS-AzLDAPQuery
member
84 Dynamic Group Support