Chapter8 E stablishing CiscoSecure ACS System Configuration
RDBMS Synchronization
8-30
Cisco Secure ACS 3.0 for Windows 2000/NT Servers User Guide
78-13751-01, Version 3.0
Step 4 Validate your third-party system to ensure that it updates the accountActions table
properly. Rows generated in the accountActions table must be valid. For details
on the format and content of the accountActions table, see Appendix G, “ODBC
Import Definitions.”
Note After testing that the third-party system updates the accountActions
table properly, discontinue updating the accountActions table until
after you have completed Step 5 and Step 6 below.
Step 5 Set up a system DSN on the Cisco Secure ACS server. For steps, see the
“Configuring a System Data Source Name for RDBMS Synchronization” section
on page 8-32.
Step 6 Schedule RDBMS synchronization in Cisco Secure ACS. For steps, see the
“Scheduling RDBMS Synchronization” section on page 8-37.
Step 7 Configure your third-party system to begin updating the accountActions table
with information to be imported into the CiscoSecure user database.
Step 8 Confirm that RDBMS synchronization is operating properly by monitoring the
RDBMS Synchronization report in the Reports and Activity section. For more
information about the RDBMS Synchronization log, see the “RDBMS
Synchronization Log” section on page 9-16.
Also, monitor the CSDBSync service log. For more information about the
CSDBSync service log, see the “Service Logs” section on page 9-34.
Considerations for Using CSV-Based Synchronization
The behavior of the Microsoft ODBC driver for text files creates significant
additional considerations if you are planning to use a CSV-based accountActio ns
table. The Microsoft ODBC driver for text files always operates in a read-only
mode. It cannot delete records from a CSV accountActions table. Because of this,
synchronization events initiated or scheduled in the HTML interface never release
the CSV file, so the updates to the accountActions table from your third-party
system fail.