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

Table 24-3 Predefined FSM Tables (continued)
FunctionFilename
Sample FSM file required to implement accounting without session
management using SQL access
/opt/aaa/examples/config/
sqlacess-acct.fsm
Sample FSM file required to implement accounting with session
management using SQL access
/opt/aaa/examples/config/
sqlaccess-acct-sess.fsm
To use any of the above predefined state tables for the HP-UX AAA server, copy the
required .fsm file to /etc/opt/aaa/radius.fsm and start the AAA server
NOTE: The product is installed with logall.fsm as radius.fsm in /etc/opt/
aaa/.
Custom State Tables
The server can be set up for different functions by modifying existing FSM tables, or
creating new FSM tables. Edit the state table for authorization sequence, or to have
interim accounting messages logged by calling the appropriate module at a certain
point in the authentication process.
Tracking Versions
You can embed version information into a state table using the following syntax:
%FSMID Version
Version
Can be any string and will appear as the ID in radcheck output.
Examples
State table modifications can range from simple to more involved customization and
offer a great deal of flexibility when configuring the HP-UX AAA software.
Preprocessing Module
An Access-Request message may need to be pre-processed for a variety of reasons. For
example, if the client sends a User-Name value with extraneous information, the
extraneous information may need to be stripped out before the server authenticates
the user. Preprocessing requires that you write or obtain a plug-in that will parse the
message and pass the processed A-V pairs to the iaaaUsers action.
Modify the state table to call the preprocessing plug-in when the message is first
received. Add a preprocessing state that calls the iaaaUsers action and transitions
to the UsersCheck state.
Custom State Tables 279