Hi, I am an Active Directory administrator with a minimal knowledge of Adobe LiveCycle (sorry!)
Our Organisation has purchased a product that uses Adobe LiveCycle for user authentication and management and the third party company implementing it were responsible for synchronising LiveCycle with our Active Directory. We required the third party to provide resilience as the product is a crucial line-of-business application, which they did by configuring LiveCycle to synchronise against two of our Domain Controllers.
The two Domain Controllers are on seperate sites (which is good practice for resilience) but what it appears is happening is that LiveCycle is synchronising the users' details from the first Domain Controller (DC1), then overwriting it with the details from the second (DC2). As DC2 is in a seperate site, there is up to a 15 minute delay between a change being made to DC1 and that change being replicated to DC2.
What was happening in practice was that the administration staff were adding a user to the Active Directory group that grants access to the product, triggering a synchronisation of LiveCycle with Active Directory and the group membership was overwritten by the details on DC2.
Is there any way of configuring LiveCycle to have a list of Active Directory Domain Controllers which it will attempt to connect to in sequence until it finds one that will respond?
Many thanks!