Appendix F RDBMS Synchronization Import Definitions
Action Codes
F-4
User Guide for Cisco Secure ACS for Windows Server
78-14696-01, Version 3.1
accountActions Processing Order
Cisco Secure ACS reads rows from accountActions and processes them in a
specific order. Cisco Secure ACS determines the order first by the values in the
Priority fields (mnemonic: P) and then by the values in the Sequence ID fields
(mnemonic: SI). Cisco Secure ACS processes the rows with the highest Priority
field. The lower the number in the Priority field, the higher the priority. For
example, if row A has the value 1 in its Priority field and row B has the value 2 in
its Priority field, Cisco Secure ACS would process row A first, regardless of
whether row B has a lower sequence ID or not. If rows have an equal priority,
Cisco Secure ACS processes them by their sequence ID, with the lowest sequence
ID processed first.
Thus, the Priority field (P) enables transactions of higher importance to occur
first, such as deleting a user or changing a password. In the most common
implementations of RDBMS Synchronization, a third-party system writes to
accountActions in batch mode, with all actions (rows) assigned a priority of zero
(0).
Note
When changing transaction priorities, be careful that they are processed in the
correct order; for example, a user account must be created before the user
password is assigned.
You can use the MessageNo field (mnemonic: MN) to associate related
transactions, such as the addition of a user and subsequent actions to set password
values and status. You can use the MessageNo field to create an audit trail for a
third-party system that writes to accountActions.
Action Codes
This section provides the action codes valid for use in the Action field (mnemonic:
A) of accountActions. The Required column uses the field mnemonic names to
indicate which fields should be completed, except for the mandatory fields, which
are assumed. For more information about the mnemonic names of accountActions
fields, see
Table F-1
. For more information about the mandatory fields, see
accountActions Mandatory Fields, page F-3
.
