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

AATV Components
An AATV is implemented as a shared library that contains specific functions. These
functions are called from the HP-UX AAA Server. An AATV can contain the following
functions:
• “The init Function.”
• “The action Function.”
• “The timer or callback Function” (page 450)
• “The cleanup Function” (page 450)
NOTE: These functions are optional. However, you must implement at least one of
these functions.
The init Function
The init function establishes the environment required for other AATV functions.
The init function is commonly used to open sockets and to create or open files for
writing, or reading module specific configurations.
Following is the prototype of the init function:
void myinit();
The action Function
The action function responds immediately to a received RADIUS request. Following
is the prototype of the action function:
static int myaction(sdk_authreq_t *authreq, int value, const
char *string);
Following are the input parameters:
authreq A pointer to the authreq
value The Xvalue from the FSM table for this action if configured. If not, 0 is
passed in by the Server.
string This parameter can have one of the following values:
• The Xstring from FSM table if the AATV is configured in the FSM.
• The Xstring from authfile if the AATV is configured to process an
authentication request.
• If the Xstring parameter is not configured, NULL is passed.
The action function returns an event code. This event code determines the next action
to be taken in the FSM. Following are the two commonly used event codes:
AAA_EV_ACK Defined as 0. It indicates that the operation is successful.
AAA_EV_NAK Defined as –1. It indicates that the operation failed.
SDK Concepts 449