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

See the README files for the supported environments in the respective directories at
/opt/aaa/examples/sqlaccess/ for specific shared library path configuration
information for the supported database clients.
Database Client Connector Libraries
For each supported database client, HP provides a corresponding client connector
library. Copy the corresponding client connector library from /opt/aaa/lib/dbcon/
alternate/ to the execution directory /opt/aaa/lib/dbcon. See the README
files in the respective directory for the supported environments at /opt/aaa/
examples/sqlaccess/ for specific client configuration.
NOTE: HP recommends that you only install one connector library to avoid
co-existence problems with multiple database client vendors.
SQL Access Implementation Details
Follow the steps below to set up and configure SQL Access:
1. Install the sample implementation. See the README files in the respective directory
for the supported environments at /opt/aaa/examples/sqlaccess/ for
specific implementation information.
Review the sample implementation, and note any modifications and customizations
required for your specific implementation. See “SQL Access Implementation
Details” (page 217) for information on the functionality provided by the sample
implementation. If you need to customize the sample implementation, continue
with steps 2 to 5.
2. Create or modify the database tables based on your implementation of SQL Access.
You can use the sample schema provided in the sample configuration files located
at /opt/aaa/examples/sqlaccess/oracle-1/ or /opt/aaa/examples/
sqlaccess/mysql-1 as a starting point.
3. Create or modify the /etc/opt/aaa/sqlaccess.config file. This file contains
database connection definitions, SQL action definitions, and an optional global
definition. See “sqlaccess.config File Configuration” (page 218) for detailed
information on the sqlaccess.config file structure.
4. Configure SQL Access execution based on your implementation:
• If SQL Access is used to retrieve user profiles, configure the SQL action for
the desired realm on the Local Realm screen in the Server Manager. See
“Adding a Realm” (page 89) for more information.
• If SQL Access is used for more advanced implementations, such as accounting
and session management, modify the Finite State Machine (FSM) radius.fsm
file to specify the execution of specific SQL actions for particular events. See
“Finite State Table Configuration in the FSM” (page 235) for more information.
The sample implementation includes two modified FSMs configured for
Implementing SQL Access 217