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.06.02 Administrator's Guide: HP-UX 11i v1 and 11i v2 > 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 three primary components:

  • Configuration files. Edit these flat text files to provide the information necessary for the server to perform authentication, authorization, and accounting requests for your system.

  • AATV plug-ins. Use the plug-ins to perform discrete actions; such as initiating an authentication request, replying to an authentication request, or logging an accounting record.

  • The software engine, which includes the Finite State Machine (FSM) and some associated routines. At server startup, the finite state machine reads instructions from a state table—by default the /etc/opt/aaa/radius.fsm text file. The state table outlines what AATV actions to call and what order to call them in.

NOTE: An SDK is available for the HP-UX AAA Server. Contact your HP sales representative for more information, or send an email request to: aaainfo@cup.hp.com.

When the server is initialized, it performs a few distinct operations. It loads and initializes the AATV plug-ins, so that actions called by the FSM are executed. 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 Authentication Process

Authentication Process

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

Configuration Files

See Chapter 23 “Configuration Files ” for detailed information on these 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 from information by several different storage methods.

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

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 of the HP-UX AAA Server to customize your server configuration without programming software modules. See Chapter 22 “The Finite State Machine (FSM) ” for more information on the Finite State Machine.

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