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
Removing the GCS from the Search Scope
To remove the GCS from the search scope, either run setup to re-configure, or manually edit
/etc/opt/ldapux/ldapux_client.conf to remove the gc section, its corresponding profiles
(/etc/opt/ldapux/domain_profiles/ldapux_profile.bin.gc and
ldapux_profile.ldif.gc), and all entries to the end of the file. Restart the client daemon
for the change to take effect.
Adding POSIX Attributes to the Global Catalog
If you select GCS to support LDAP-UX integration with ADS multiple domains, you should add
POSIX attributes into the global catalog. The needed attributes are those used by getXbyY()
APIs to return data. For LDAP-UX B.03.00 or later, only passwd andgroup are supported in
multiple domains. Therefore, the following POSIX attributes must be added into the global
catalog:
• For SFU version 2.0:
msSFUName - used by getpwnam() and getgrnam()
uidNumber - used by getpwuid()
gidNumber - used by getgrgid()
• For SFU version 3.0 or 3.5:
msSFU30Name - used by getpwnam() and getgrnam()
msSFU30uidNumber - used by getpwuid()
msSFU30gidNumber - used by getgrgid()
• For Windows Server 2003 R2's RFC2307 :
uid - used by getpwnam() and getgrnam()
uidNumber - used by getpwuid()
gidNumber- used by getgrgid()
To add these attributes to the global catalog:
1. On your Windows 2000 GCS, click Start, then Run. In the open dialog box, type mmc, then
click OK.
2. Click the Microsoft Management Console menu, select Add/Remove Snap-in.
3. Click Add under the Standalone tab to get to the Add Standalone Snap-in dialog box.
4. In the Add Standalone Snap-In dialog box, select Active Directory Schema, then click Add
and then Close.
5. Active Directory Schema appears in the Add/Remove Snap-In dialog box. Click OK.
6. In the Microsoft Management Console, click Active Directory Schema and Double-click
Attribute, under Name on the right-hand side of the box. All attributes will be shown..
7. Click the POSIX attribute to add into the global catalog (for example; msSFUname for SFU
2.0, uidNumber, gidNumber), and then select Properties from the Action menu.
8. In the Attribute Properties dialog box, select Replicate this attribute to the Global Catalog
and Index this attribute in the Active Directory, click Apply, and then OK.
9. Repeat steps 6 and 7 until all the required POSIX attributes are added into the global catalog.
Limitations of Multiple Domains in Version B.03.00 or later
• LDAP-UX Client Services only supports passwd and group in ADS multiple domains.
• LDAP-UX Client Services using Windows 2000 or 2003 Active Directory Server does not
support netgroup service data.
62 Active Directory Multiple Domains