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

33 Configuration Files
The Server Manager interface configures most of the HP-UX AAA Server’s configuration files.
However, some features of the HP-UX AAA Server cannot be configured through the Server Manager
interface. If you want to define policy, vendor-specific attributes, or logging behavior, you must
manually edit the configuration files. The information in this chapter is provided as a reference for
the configuration files that Server Manager cannot configure.
Following lists the configuration files that you must manually edit from the command line:
• radius.fsm — see Chapter 26: “Customizing the HP-UX AAA Server Using the Finite State
Machine” (page 290)
• “The dictionary File ” (page 390)
• “The las.conf File ” (page 393)
• “The vendors File ” (page 395)
• “The log.config File ” (page 396)
The following is a list of the configuration files that you can edit from the command line after editing
them with Server Manager. Some features are not configurable through Server Manager, therefore
additional command line editing is sometimes required:
• “The aaa.config File” (page 382)
• “The clients File” (page 386)
• “The users File ” (page 388)
• “sqlaccess.config Sample File” (page 250)
NOTE: If the configuration files in /etc/opt/aaa directory are incorrectly configured or deleted
during the course of configuring AAA Server, you can get the original configuration files as provided
during installation from the /opt/aaa/newconfig/etc/opt/aaa directory.
HUP Processing
The HUP signal (kill -HUP) provides the ability to update some of your configuration while the AAA
server is running. The signal tells the AAA server a process a change occurred and to read
configuration files again. The HUP signal will read the following files:
• users
• clients
• authfile
• aaa.config
• engine.config (all values except the certificate properties, which require a server stop and
start to be refreshed)
• las.conf
• EAP.authfile
• aaa.config.license
• sqlaccess.config
HUP Processing 381