HP-UX AAA Server A.08.00.01 Administrator's Guide

Figure 26-1 Default FSM State Transitions
The actions triggered during this process read information from the server’s
configuration, and from stored user profiles, and policy. Based on this information the
actions perform the server’s authentication, authorization, and accounting functions.
The server can be set up to do a variety of different functions by modifying existing or
creating new FSM state tables. For example, interim accounting messages can be logged
by calling the appropriate module at a certain point in the authentication process.
Each state defined in a finite state table starts with a line containing the name of the
state, followed by a colon character. Each subsequent line is an event handler with
three required and two optional fields, delimited by spaces or tabs. Below is the syntax
of a state in a finite state table:
State-name:
Event-1 Action-1 Next-state-1 Xvalue=integer Xstring=string
... ... ...
Event-n Action-n Next-state-n Xvalue=integer
Xstring=string
States 391