Safeguard Authentication Services provides a feature called "mapped user" where you can map local UNIX user accounts to Active Directory user accounts. Local users retain all of their local UNIX attributes such as UID Number and Login Shell, but they authenticate using their Active Directory password. Active Directory password policies are enforced. You can map users by editing configuration files on the UNIX host.
Advantages of mapped users:
-
Provides a rapid deployment path to take advantage of Active Directory authentication
-
Kerberos authentication provides stronger security
-
Enables centralized access control
-
Enforces Active Directory Password policies
-
Provides a path for consolidating identities in Active Directory with Ownership Alignment Too (OAT)
-
Low impact to existing applications and systems on the UNIX host
-
Easy to deploy with self-enrollment
By mapping a local user to an Active Directory account, the user can log in with their UNIX user name and Active Directory password.
NOTE: Active Directory password policies are not enforced on HP-UX systems that do not have PAM requisite support. To prevent users from authenticating with their old system account password after mapping, install the freely available PAM Requisite package provided by HP.