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

Migrating Plug-ins Created Using Previous Versions of the SDK
Plug-ins created using previous versions of the SDK must be ported to use the new
SDK and recompiled before using it with HP-UX AAA Server A.07.01. For information
on recompiling your plug-in, see “Compiling and Loading a Plug-in” (page 321)
Prerequisites for Using the SDK
HP recommends installing the HP aC++ Compiler (# B3913DB) to compile plug-ins
created using the HP-UX AAA Server SDK.
SDK Directory Structure
The HP-UX AAA Server SDK consists of the following files and directories:
• The /opt/aaa/include/sdk.h header file
• The following sample plug-ins:
— /opt/aaa/examples/sdk/CSI/checkCSI.c
— /opt/aaa/examples/sdk/ace/samplesc.c
• READMEs that describe the sample AATVs
Important Note:
For information on the header files, data structures, and APIs included with the SDK,
see Appendix D (page 430).
SDK Concepts
This section explains how the plug-ins interface with the HP-UX AAA Server operation.
To ensure that the HP-UX AAA Server processes the functions included in your plug-ins,
you can modify the state tables in the Finite State Machine (FSM) to refer to the functions
(actions) defined in your custom plug-ins, or you can add it to the authfile for
authentication AATVs. Modified FSM tables can include instructions to add or change
the order of the processing steps. Plug-ins can be inserted as steps anywhere in the
FSM table. AATVs are directly referenced as actions in the FSM table. For more
information on AATVs, see “Overview of AATVs.”
Overview of AATVs
An AATV is a framework for various functionalities, such as password validation.
These AATVs are functional blocks that perform basic AAA functions, such as
authentication, authorization, and accounting. However, an AATV's functions are not
limited to these. This framework provides you enough flexibility to add your own
plug-ins as well.
Migrating Plug-ins Created Using Previous Versions of the SDK 317