HP-UX AAA Server A.08.00.01 Release Notes

EAP-SIM and EAP-AKA authentication methods
HP-UX AAA Server A.08.00.01 supports the Extensible Authentication Protocol
Subscriber Identity Module (EAP-SIM) as specified in RFC 4186 and Extensible
Authentication Protocol Authentication Key Agreement (EAP-AKA) as specified in
RFC 4187. EAP-SIM and EAP-AKA enable usage of mobile network authentication
infrastructure for secure access to wireless LAN. EAP-SIM provides more reliable
security using the underlying Global System for Mobile Communications (GSM)
authentication and key agreement mechanism. EAP-AKA enhances the third generation
Authentication and Key Agreement mechanism used for Universal Mobile
Telecommunications System (UMTS) and CDMA2000 networks.
EAP-SIM and EAP-AKA include the following key features:
• In-built key generation (A3/A8/AKA) algorithm that can be customized or replaced
with operator-specific algorithm using HP-UX AAA Server A.08.00.01 Software
Development Kit (SDK).
• The Users credential (Ki) can be retrieved from the supported data stores like
SQL-compliant database server. The credential can also be retrieved from external
storage like an Authentication Center (AuC), if a plug-in is implemented using
HP-UX AAA Server SDK.
• In-built support for an optional identity privacy support using pseudonym identity
and an optional fast re-authentication procedure on per-realm basis.
For more information on the EAP-SIM and EAP-AKA authentication methods, see the
“Configuring EAP-SIM and EAP-AKA Authentication Methods” chapter in the HP-UX
AAA Server A.08.00.01 Administrator’s Guide.
Scalability and High Availability
HP-UX AAA Server A.08.00.01 supports scalability and high-availability.
Scalability is achieved by supporting multiple HP-UX AAA Servers on the same host
and high-availability is achieved by supporting cloned HP-UX AAA Servers on the
same or different hosts.
HP-UX AAA Server supports running multiple HP-UX AAA Servers on a single host,
thereby ensuring optimum utilization of system resources and addressing the
organizational scalability requirements.
HP-UX AAA Server can be cloned on the same host or on a different host for
high-availability. If the primary HP-UX AAA Server fails or during HP-UX AAA Server
maintenance, the cloned HP-UX AAA Servers serve as backup, and process client
requests. If the host on which the primary HP-UX AAA Server is running fails, a clone
running on a different host can serve as a backup. This ensures high-availability of the
solution.
For more information on scalability and high-availability, see the “Configuring HP-UX
AAA Server for Scalability and High-Availability” chapter in the HP-UX AAA Server
A.08.00.01 Administrator’s Guide.
What is New in This Version 9