HP-UX AAA Server Architecture

The HP-UX AAA Server Architecture consists of three primary components:

Configuration files. Files to provide the information necessary for the server to perform authentication, authorization, and accounting requests for your system. In most cases these files can be modified via the Server Manager.
AATV plug-ins. Dynamically loaded libraries that perform discrete actions; such as initiating an authentication request, replying to an authentication request, or logging an accounting record.
The radiusd software engine, which includes the Finite State Machine (FSM) and associated routines. At server startup, the FSM reads instructions from the state table in the /etc/opt/aaa/radius.fsm configuration file. The state table outlines what AATV actions to call and what order to call them in.

When the server is initialized, it loads and initializes the AATV plug-ins. It also reads the configuration files to initialize the data required for the actions to execute according to the application's requirements.

Figure 1-3 illustrates the general process of server initialization and response to an authentication request:

Figure 1-3 Authentication Process

Figure 1-3 “Authentication Process” illustrates the general process of server initialization and response to an authentication request.

Configuration Files

See Chapter 28 “Configuration Files ” for detailed information on the server configuration files.

AATV Plug-Ins

An AATV plug-in defines the actions that perform a variety of functions, including authenticating requests, authorization, and logging. Built-in actions support authentication of users using information from several different repositories, and accounting requests using several different polices and storage formats.

See “Actions ” for more information on these built-in actions.




	NOTE: HP provides an SDK for creating your own AATV plug-ins to the HP-UX AAA Server. Contact your HP sales representative for more information, or send an email request to aaainfo@cup.hp.com.

The Software Engine: Finite State Machine

The FSM controls the step-by-step process that the server follows to process and respond to an authentication request. You can configure the FSM to customize your server configuration without programming software modules. See Chapter 27 “The Finite State Machine (FSM) ” for more information on the Finite State Machine.

HP-UX AAA Server Architecture

Technical documentation

» Table of Contents

» Glossary

» Index

Configuration Files

AATV Plug-Ins

The Software Engine: Finite State Machine