Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX AAA Server A.08.00.01 Administrator’s Guide: HP-UX 11i v2 and HP-UX 11i v3 > Chapter 1 Overview: The HP-UX AAA Server

HP-UX AAA Server Architecture

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

The HP-UX AAA Server architecture consists of the following 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 by using 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

Authentication Process

Configuration Files

For detailed information on the server configuration files, Chapter 33: “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.

For more information on these built-in actions, see “Actions ”

The Software Engine: Finite State Machine

The Finite State Machine (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. For more information on the Finite State Machine, see Chapter 26: “Customizing the HP-UX AAA Server Using the Finite State Machine”.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.