What is New in This Version

Dynamic Authorization

HP-UX AAA Server A.08.00.01 supports dynamic authorization, which is based on the client functionality of the HP-UX AAA Server.

RFC 5176 defines new RADIUS standards that support RADIUS server-initiated requests. These RADIUS server-initiated requests can be used to send Disconnect packets to disconnect user sessions, or to send Change-Of-Authorization (CoA) packets to change the authorization attributes of the user sessions. The HP-UX AAA Server implements the dynamic authorization capability to send requests to the authenticator, to disconnect user sessions or to change the session attributes.

For more information on how the dynamic authorization capability of the HP-UX AAA Server works, see the “Configuring the HP-UX AAA Server for Dynamic Authorization” chapter in the HP-UX AAA Server A.08.00.01 Administrator’s Guide.

For more information on how the client functionality of the HP-UX AAA Server works, see the “Configuring the HP-UX AAA Server for Client Functionality” chapter in the HP-UX AAA Server A.08.00.01 Administrator’s Guide.

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:

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.

MS-CHAP v2 for OTP Authentication

HP-UX AAA Server A.08.00.01 supports MS-CHAP v2 for OTP authentication. OTP support for MS-CHAP v2 is compatible with RFC 4226.

The following functions are supported for MS-CHAP v2:

For more information on MS-CHAP v2 for OTP Authentication, see the “OATH Standards-Based OTP Authentication” chapter in the HP-UX AAA Server A.08.00.01 Administrator’s Guide.