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

Table Of Contents
authentication mechanism, specify the realm name in the request-ingress.grp as
follows:
if ( (count (User-Name) > 0) && (substr (User-Name after "@" ) = "otprealm" ) )
Specify the realm name in the reply-egress.grp file as follows:
if ( (count (User-Realm) > 0) && (User-Realm = "otprealm"))
NOTE: Creating different inner and outer realms for OTP authentication is supported
only for TTLS (PAP and MS-CHAP v2). For information on creating tunneled EAP
realms, see Adding a Realm” (page 105).
If you are proxying the OTP to a remote server for validation, you must modify the
reply-egress.grp file:
if ( (count(Interlink-Proxy-Action) > 0) && ( (Interlink-Proxy-Action = "ACCT")
|| (Interlink-Proxy-Action = "LAS_ACCT") )
|| ( (count (User-Realm) > 0) && (User-Realm = "otprealm" ) ) )
NOTE:
When a response from the proxy is returned, the HP-UX AAA Server implements
the reply-egress policy, and does not increment the sequence counter and the
success or failed authentication counters (since they are incremented by the external
RADIUS server).
User Level OTP Attributes
To configure OTP attributes on a user level, you must modify the RetrieveToken
SQLAction in the sqlaccess.config file. You can choose to include the user-specific
OTP attributes, listed in Table 16-4 (page 192), using the following syntax:
198 OATH Standards-Based OTP Authentication