HP-UX AAA Server A.08.01 administrator's guide (T1428-90072, May 2010)

Table Of Contents
Figure 16-1 OATH Standards-Based OTP Authentication Flow and the HP-UX AAA Server.
Following is the OTP authentication process flow:
1. The user requests access to a protected resource by sending the user credentials
(password or OTP, or password and OTP), which is encrypted with the shared
secret, to the authenticator.
The OTP can contain either six, seven, or eight digits.
2. The authenticator forwards the request to the HP-UX AAA Server.
3. The HP-UX AAA Server validates the OTP and password locally.
NOTE:
a. If RADIUS standard Password Authentication Protocol (PAP) is used, the
HP-UX AAA Server can split the user password in to password and OTP and
perform one of the following actions:
Validate the OTP, or password, or password and OTP.
Proxy the OTP or password to an external RADIUS server for validation.
Splitting of the user password into password and OTP is not supported for
MS-CHAP v2 authentication protocol as the user password is a hash. Therefore,
partial validation of either OTP or password locally and the remaining part at
an external RADIUS server is not possible. The complete validation must be
performed at the local HP-UX AAA Server or at an external RADIUS server.
b. The HP-UX AAA Server can be configured to generate OTPs that can be
delivered to customers through the secondary channel using SMS, e-mail, FTP,
and so on. Contact your HP Support representative for assistance while
configuring the HP-UX AAA Server to use the secondary channel for OTP
delivery.
If the validation is performed locally, the HP-UX AAA Server updates the database
with the incremented sequence counter after successful OTP authentication. If the
validation is performed by an external RADIUS server, the external RADIUS server
updates the database with the incremented sequence counter after successful OTP
authentication.
HP-UX AAA Server and OATH Support 181