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

Table 26-1 Predefined Event Names (continued)
DescriptionEvent Name
The incoming Accounting-Request that the user has been
denied access to an established tunnel.
ACT_TUNNEL_LINK_REJECT
The incoming request is an Access-Request.
AUTHEN
Received Access-Request has a Status-Type of
Authenticate-Only.
AUTH_ONLY
The incoming Access-Request is a continuation of an
in-progress EAP conversation. In general, you can allow
CONTINUE
the server to handle these events without any modification.
This event is not pre-defined, it must be defined in the
FSM file.
The request is a CLIENT request.
CLIENT_REQ
The request must be dropped without any further
processing. This event is not pre-defined, it must be
DROP
defined in the FSM file with a value that matches the value
of DROP for the Interlink-Reply-Status attribute
defined in the dictionary file.
The incoming Access-Request is a duplicate. Generally,
you should allow the server to handle these events without
modification.
DUP
The previous action generated an error. Generally, you
can allow the server to handle these events without
modification.
ERROR
The incoming Accounting-Request is an
accounting-interim-update. Generally, you can allow the
LASCP
server to handle these events without modification. This
event is not pre-defined, it must be defined in the FSM
file.
Negative acknowledgment of the previous action.
NAK
This event is returned by the REALM Action when a user's
realm cannot be found in the authfile.
NO_SUCH_REALM
Event Names 401