This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
  • RSA.com
  • Home
  • Advisories
    • SecurID
    • SecurID Governance & Lifecycle
  • Documentation
    • SecurID
      • Authentication Agents
        • API / SDK
        • Apache Web Server
        • Citrix StoreFront
        • IIS Web Server
        • MFA Agent for macOS
        • MFA Agent for Windows
        • Microsoft AD FS
        • Microsoft Windows
        • PAM
      • Authentication Engine
      • Authentication Manager
      • Cloud Authentication Service
      • Hardware Appliance
        Component Updates
      • Hardware Tokens
      • Integrations
      • SecurID App
      • SecurID Authenticator for macOS
      • SecurID SDK
      • Software Tokens
        • Android
        • iOS
        • macOS
        • Token Converter
        • Windows
    • SecurID Governance & Lifecycle
    • Technology Partners
  • Downloads
    • SecurID
      • Authentication Agents
        • API / SDK
        • Apache Web Server
        • Citrix StoreFront
        • IIS Web Server
        • MFA Agent for macOS
        • MFA Agent for Windows
        • Microsoft AD FS
        • Microsoft Windows
        • PAM
      • Authentication Engine
      • Authentication Manager
      • Cloud Authentication Service
      • Hardware Appliance
        Component Updates
      • Hardware Tokens
      • Integrations
      • SecurID Authenticator for macOS
      • Software Tokens
        • Android
        • iOS
        • macOS
        • Token Converter
        • Windows
    • SecurID Governance & Lifecycle
  • Community
    • SecurID
      • Blog
      • Discussions
      • Events
      • Idea Exchange
      • Knowledge Base
    • SecurID Governance & Lifecycle
      • Blog
      • Discussions
      • Events
      • Idea Exchange
      • Knowledge Base
  • Support
    • Case Portal
      • Create New Case
      • View My Cases
      • View My Team's Cases
    • Community Support
      • Getting Started
      • News & Announcements
      • Ideas & Suggestions
      • Community Support Articles
      • Community Support Forum
    • Product Life Cycle
    • Support Information
    • General Security Advisories
  • Education
    • Blog
    • Browse Courses
      • SecurID
      • SecurID Governance & Lifecycle
    • Certification Program
    • New Product Readiness
    • Student Resources
Sign In Register Now
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements

SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
  • SecurID Community
  • :
  • Products
  • :
  • SecurID
  • :
  • Discussions
  • :
  • Limits of replica appliance
  • Options
    • Subscribe to RSS Feed
    • Mark Topic as New
    • Mark Topic as Read
    • Float this Topic for Current User
    • Bookmark
    • Subscribe
    • Mute
    • Printer Friendly Page
HEATHCARSON
HEATHCARSON New Contributor
New Contributor
‎2017-04-17 04:13 PM
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Limits of replica appliance

Jump to solution

We're using RSA SecurID Appliance version 3.1 running Auth Manager 7.1. We have a primary and a replica. Questions are: 

How long can the authentication replica service requests without having contact with the primary?

In what ways is the replica limited vs the primary. I.E. what functions can you not perform on the replica?

  • Tags:
  • Community Thread
  • Discussion
  • Forum Thread
  • RSA SecurID
  • RSA SecurID Access
  • SecurID
0 Likes
Share
Reply
  • All forum topics
  • Previous Topic
  • Next Topic
1 Solution

Accepted Solutions
JayGuillette
Apprised Contributor JayGuillette Apprised Contributor
Apprised Contributor
‎2017-04-17 04:20 PM
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Jump to solution

A replica is a read only copy of the primary database, used to authenticate users on agents, but you cannot administer on a replica, cannot add new people, agents, assign tokens, etc...

A replica can be promoted to primary, either as a disaster recovery meaning the primary is dead, or a maintenance, meaning you want to attach the old primary as a replica to the newly promoted replica

 

The good thing about Auth manager is also the bad thing, it just keeps running.  AM 7.1 is at least 4 years out of date, maybe a lot more.  you'll need to look at migrating your 7.1 database to at least version 8.1 SP1 P15

View solution in original post

2 Likes
Share
Reply
4 Replies
JayGuillette
Apprised Contributor JayGuillette Apprised Contributor
Apprised Contributor
‎2017-04-17 04:20 PM
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Jump to solution

A replica is a read only copy of the primary database, used to authenticate users on agents, but you cannot administer on a replica, cannot add new people, agents, assign tokens, etc...

A replica can be promoted to primary, either as a disaster recovery meaning the primary is dead, or a maintenance, meaning you want to attach the old primary as a replica to the newly promoted replica

 

The good thing about Auth manager is also the bad thing, it just keeps running.  AM 7.1 is at least 4 years out of date, maybe a lot more.  you'll need to look at migrating your 7.1 database to at least version 8.1 SP1 P15

2 Likes
Share
Reply
JayGuillette
Apprised Contributor JayGuillette Apprised Contributor
Apprised Contributor
In response to JayGuillette
‎2017-04-17 04:22 PM
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Jump to solution

also, if replication is broken, i.e. the primary is not sending changes to the replica, then your replica is getting out of date...if your site is stable this will only be a small problem, but with a big risk.  If your site changes often this is a bigger problem with bigger risk.  Look in Operations Console - Deployment Config - Instances - Status report to see if OK.  

2 Likes
Share
Reply
BrianTwomey
Employee BrianTwomey
Employee
‎2017-04-17 04:57 PM
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Jump to solution

Another thing to be aware of in 7.x....the Primary will only keep so many days of data in queue for the replica...once that data gets overwritten the replica will be unrecoverable and must detached/reattached.....not to mention that the archive log table will continue to grow (on Primary) and if that hits 100 GB, the Primary will no longer function.

2 Likes
Share
Reply
EdwardDavis
Employee EdwardDavis
Employee
‎2017-04-18 08:12 AM
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Jump to solution

a) a replica without a primary will authenticate things already in it's database indefinitely...forever it you want it to

 

b) a replica is in read only mode, no administrative actions can be done on a replica except things initiated by a user login action,

and that are already in some sort of change required mode, such a set a user pin/change a pin or lock out a user. 

2 Likes
Share
Reply
Powered by Khoros
  • Blog
  • Events
  • Discussions
  • Idea Exchange
  • Knowledge Base
  • Case Portal
  • Community Support
  • Product Life Cycle
  • Support Information
  • Customer Success
  • About the Community
  • Terms & Conditions
  • Privacy Statement
  • Provide Feedback
  • Employee Login
© 2022 RSA Security LLC or its affiliates. All rights reserved.