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.07.00 Administrator's Guide: HP-UX 11i v1, 11i v2, and 11i v3 > Chapter 27 The Finite State Machine (FSM)

Event Names

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

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 the server to return predefined or custom event names by using the Decision attribute in stored policy.

Predefined Names

Several event names that can be returned by an action are predefined in the server.

Table 27-1 Predefined Event Names

Event Name Description
ACCTThe incoming request is an Accounting-Request.
ACC_CHAL Access-Challenge message must be sent in response to an access challenge.
ACCT_ALIVE The incoming Accounting-Request is an interim accounting message.
ACCT_CANCEL The incoming Accounting-Request is a message to cancel the session.
ACCT_DUPThe incoming Accounting-Request is a duplicate.
ACCT_MSTARTThe originating NAS has just rebooted, so all active sessions from this client can be purged.
ACCT_MSTOPThe originating NAS is about to reboot.
ACCT_OFFReceived accounting message has a Status-Type of Accounting-Off.
ACCT_ONReceived accounting message has a Status-Type of Accounting-On.
ACCT_STARTReceived accounting message has a Status-Type of Start.
ACCT_STOPReceived accounting message has a Status-Type of Stop.
ACCT_TUNNEL_LINK_STARTThe incoming Accounting-Request is a message to start a session through an established tunnel.
ACCT_TUNNEL_LINK_STOPThe incoming Accounting-Request is a message to end a session through an established tunnel.
ACCT_TUNNEL_REJECTThe incoming Accounting-Request indicates that a requested tunnel could not be established.
ACCT_TUNNEL_STARTThe incoming Accounting-Request is a message to establish a tunnel.
ACCT_TUNNEL_STOPThe incoming Accounting-Request is a message to eliminate a tunnel.
ACKAcknowledgment of the previous action.
ACT_TUNNEL_LINK_REJECTThe incoming Accounting-Request that the user has been denied access to an established tunnel.
AUTHENThe incoming request is an Access-Request.
AUTH_ONLYReceived Access-Request has a Status-Type of Authenticate-Only.
DUPThe incoming Access-Request is a duplicate. Generally, you should allow the server to handle these events without modification.
ERRORThe previous action generated an error. Generally, you can allow the server to handle these events without modification.
NAKNegative acknowledgment of the previous action.
NO_SUCH_REALMThe NO_SUCH_REALM value is returned by the REALM Action when a user's realm cannot be found in the authfile.
PW_EXPIREDThis value is returned by the AUTHENTICATE Action if the user profile includes an out-of-date value for the Expiration configuration attribute.
RETRIEVE_SUCCESSThis value is returned by iaaausers, ORACLE, PROLDAP, SQL Access, or another data store action if the action could locate the user profile in the configured data store.
RETRIEVE_ERROR

This value is returned by iaaaUsers, ORACLE, PROLDAP, or another data store action if the action could not locate the user’s profile in the configured data store.

RETRY_LIMITThe number of received duplicate requests has exceeded the retry limit.
TIMEOUTThe request has timed out due to inactivity.
TIMERThe timer value has expired.
WAITThe previous action generated a pending event. Generally, you should allow the server to handle these events without modification.

 

Creating New Names

You can create custom event names. An event can be defined anywhere in the state table, but it must be defined before it is referenced. Use the following syntax for creating new event names:

event Name 
Name

Can be any alphanumeric string and can include underscores (_).

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