- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
External Identity Source - redundancy
Situation
DC 1 DC2
Primary - Replica
Replica Replica
Primary instance connected to identity source AD in DC1
1. DC1 Primary replicates to DC2 Replica
2. DC2 goes down
3. Promote DC2 Replica to Primary
4. Question with newly promoted DC2 Primary see DC1 identity source?
- I say no
Question - can I put the replicated DC2 AD in as the Directory Failover URL?
So if it is now, how do I replicate the external identity source that has all the tokens assigned to DC2 Primary?
Cheers
Dana Burton
- Tags:
- Authenticator
- Authenticators
- Community Thread
- Discussion
- Forum Thread
- RSA SecurID
- RSA SecurID Access
- SecurID
- Token
- Token Auth
- Token Authentication
- Token Authenticator
- Token Authenticators
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You try to configure an LDAP Identity Source that is local to the AM server, primary and replicas, with failover local if possible but remote is OK since it is failover only.
When you promote a replica, it keeps its LDAP configuration, which should have been local AD first. Inherent assumption in all this is that the LDAP servers in both locations are the 'same' identity source, so all AM users are found in same place just on different Domain Controllers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks.... that is what I thought... just need confirmation
Cheers
Dana
