HP-UX AAA Server A.08.02.10 Administrator's Guide HP-UX 11i v3 (T1428-90093, November 2013)

SQL Action Processing and Result Handling
The SQL Access AATV processes all mapping entries of an SQL action in the order in which they
are defined in the sqlaccess.config file. It first processes all input mapping entries in order, then
executes the SQL statement, and finally processes the output mapping entries in order.
SQL actions start with an event of ACK and mapping entries usually return an event of ACK. If any
mapping entry returns an event other than ACK, the SQL processing is stopped and control is
immediately returned to the FSM . You can control this behavior with customized mapping functions
to set pre-defined or custom event codes other than ACK and ACK.
If all mapping entries are processed successfully, the SQL Access AATV returns control to the FSM
at the end of the SQL action with an ACK event or a customized value for the event code.
Note that by default, the AAA Server will not take any action based on the SQL statement execution
result code returned by the database client library. However, you can configure an SQL result
output mapping to define the behavior of the AAA Server based on the SQL statement result. For
more information on how to control execution based on SQL statement result codes from SQL
statement execution, see “SQL Result Mapping” (page 267).
NOTE: An SQL query can return more than one matching row, however, only the first row of a
result is used for output mapping.
Implementing SQL Access
SQL Access requires that you configure and modify a number of mandatory and optional files
based on your implementation. HP recommends that you start with the sample implementation files
to facilitate the initial set up and configuration for SQL Access before further customization to meet
your particular business need.
Sample Implementation Files
The sample set of configuration files and scripts set up a working environment that uses SQL
statements to retrieve user and token entries, and optionally perform accounting and session
management in a multi-server environment. See “SQL Access Implementation Details” (page 255)
for more information on the functional details of the sample implementation.
There are two sets of sample configuration files:
• /opt/aaa/examples/sqlaccess/oracle-1: files to set up a sample implementation
for Oracle 10g and OCI client. See the README in that directory for detailed information on
how to install your sample SQL Access implementation for Oracle.
• /opt/aaa/examples/sqlaccess/mysql-1: files to set up a sample implementation for
MySQL and Unix ODBC driver. See the README in that directory for detailed information on
how to install your sample SQL Access implementation for MySQL.
NOTE: The database server and client are not provided with the HP-UX AAA Server. However,
HP supports connectivity to selected database clients and provides a corresponding client connector
library for those supported clients.
The following section provides an overview of the sample implementation:
sqlaccess.config Sample File
The sqlaccess.config sample file is configured for the database tables defined in the schema
files provided with this sample configuration. Its SQL actions operate on the database tables as
follow:
Implementing SQL Access 251