Issue with imported AccountActions file

Unanswered Question
Aug 9th, 2007

I'd like to know if anyone could identify the cause for the following?

We run two Secure ACS servers v4.1.3.12 (patch 2) one as primary and the other as secondary. This issue also occured in v4.1.1.23. They have no issue with replication between them.

I log onto the primary, and import an AccountActions file for adding new user accounts, which is imported successfully as noted in the RDBMS log and stating the AAA is the primary. Though the user account does not appear in the primary but appears in the secondary.

Under System Configuration -> RDBMS Synchronization Setup, the Synchronization Partners are listed as AAA Servers is primary and Synchronize is secondary.

Can anyone explain why the primary is not being updated or the new user appearing in the list? I can manually create an account on the primary and have it sync successfully to the secondary.

I've attached the accountactions file, which is reduced to one account for testing purposes.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
elvioserrao Thu, 08/09/2007 - 15:17

Problem solved.

v4.1.1.23 would not display primary in Synchronization Partners in AAA Servers, which up to v4.1.3.12 (patch 2) is now visible. Added primary to Synchronize and both are now updated.

Actions

This Discussion