Planning and Configuring HP-UX DCE 2.0

HP-UX Integrated Login
Integrating DCE with HP-UX Integrated Login
Chapter 7 95
When using passwd_import to set up accounts from /etc/passwd, be
aware that passwd_import:
• Creates accounts for all entries in /etc/passwd but marks the
accounts invalid. After using passwd_import, the cell administrator
must use dcecp to assign a password to each account and to mark
each account as valid.
• Does not create accounts from NIS information. However, you can
run passwd_import on the source file used to generate the NIS map
to import NIS information into DCE. You still have to mark valid and
assign a password to each imported account.
See the dcecp (8), passwd_export (8), and passwd_import (8) manpages or
the OSF DCE Administration Guide-Core Components for more
information on importing and exporting account information, and on
creating and modifying DCE registry accounts.
Configuring HP-UX Integrated Login with DCE
To integrate DCE with HP-UX Integrated Login in each DCE cell
member system:
• Be sure that you have completed the steps in the previous section
"Preparing to Integrate DCE with HP-UX Integrated Login".
• Follow the instructions given in the section entitled "Activating
HP-UX Integrated Login". When issuing the command to activate
HP-UX Integrated Login, substitute the string "dce" for the required
tech_name field when specifying the authentication policy.
If DCE is specified as the login technology, auth.adm performs the
following actions:
• Verifies that the system is not configured with HP-UX Commercial
Security.
• Verifies that a root account exists in the DCE Security Registry.
• Copies the root account entry in /etc/passwd to /etc/opt/dce/
passwd_override.
• Starts ilogind (the integrated login daemon) and adds it to the
startup list. The DCE backend to PAM (PAM-DCE), as well as the
DCE backend to NSS (NSS-DCE), communicate with ilogind, which