HP-UX AAA Server A.08.01 administrator's guide (T1428-90072, May 2010)

Xvalue=integer
An A-V pair (integer value) that may be passed to an Action as
an argument. Only one integer argument may be specified for
each event.
Xstring=string
An A-V pair (string value) that may be passed to an Action as
an argument. Only one string argument may be specified for
each event.
Using Xstring to call Policy
With the POLICY module, you can use the Xstring parameter to specify an URL where
policy definitions are stored. These policies group requests based on Attribute Value
(A-V) pairs in an Access-Request. These policies allow the request to be resolved
differently according to those values. For example, with some additional modifications
to the FSM you can control access based on dial-in date and time, or perform Dialed
Number Identification Service (DNIS) routing based on the number dialed, or other
such criteria.
Xstring=decisionfile:Filename
Where:
Filename The name of the file.
This syntax allows you to point to policy stored in a flat file (called a decision file, see
Chapter 27 (page 411)).
NOTE: You can configure the FSM to call the POLICY action more than once. The
FSM must call POLICY in multiple instances for each different decision file you wish
to use.
Using Xstring to Call an Alternate authfile
With the REALM action you can use the Xstring parameter to point to an alternate
authfile. Use the following syntac to use Xstring to call an alternate authfile:
Xstring=Filename
Filename is the name of the alternate file.
The authfile is used by the REALM action while processing the Authentication request.
Set Xstring with the prefix name of the authfile to use an alternate authfile instead
of the default authfile.
Event Names
After an action completes its task, it returns an event name to the FSM. The previous
state, action, and the event name determine the current event, which in turn determines
the next action of the FSM. The event names returned by the standard HP-UX AAA
Server actions are predefined, but you can create your own names by modifying the
FSM. To implement your own policy decisions or custom logging, you can configure
Event Names 399