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

sess_start_time
session_id
user_name
nasid
nasport
assigned_framed_ip
client_hw_address
client_identifier varchar2(100),
session_timeout number(11),
from_host varchar2(253),
session_status varchar2(253),
sess_mod_time TIMESTAMP,
filter_id varchar2(253)
In addition, the dbsetup.sql script for OCI creates a stored procedure to first retrieve the IP
address for a session ID and then to delete it from the session table RAD_SESS_TABLE.
Finite State Machine Sample
NOTE: If you are using SQL Access for the retrieval of user entries only, you can use your existing
FSM file.
The sample implementation contains two FSM files, one modified for accounting without session
management via SQL Access (sqlaccess-acct.fsm), and one that allows both, accounting and session
management via SQL Access (sqlaccess-acct-sess.fsm). Note that session management
with DHCP is only possible for OCI in the sample implementation, and that you need to specifically
modify sqlaccess-acct-sess.fsm to choose session management with or without DHCP. By
default session management is disabled in this FSM file.
Pre-requisites for SQL Access
SQL Access requires the following:
• Database Server and Schema
• Database Client and Client Connector Libraries
Database Server and Schema
If you are not using an existing database, see your database vendor's documentation to install the
database server software and create an instance of the database where the tables are to be
located. See the README files for the supported environments in the respective directory at /opt/
aaa/examples/sqlaccess/ for specific implementation information.
You must consider the following while selecting and setting up your database environment:
Database Security
Secure communication between the database client and the database server is controlled by the
database server and client software. Therefore, choose your database environment based on your
organization's security requirements. You may have to consider controlling access to the database
tables based on views and privileges, data encryption requirements between the database client
and server, or data encryption requirements of the data stored in the database.
254 SQL Access