Primary Instance
The primary instance is the initial AM system that you deploy. Once you deploy a primary instance, you can add replica instances. It is possible to promote a replica instance to replace the primary instance in maintenance or disaster recovery situations.
The primary instance is the only system in the deployment that allows you to perform all AM administrative tasks. Some administrative tasks can be performed on a replica instance, for example, replica promotion and log file collection.
The main functions of the primary instance include the following:
Authenticating users.
Enabling administration of AM data stored in the internal database. You can perform tasks such as importing and assigning SecurID tokens, enabling risk-based authentication (RBA), adding LDAP identity sources, configuring self-service, generating replica packages, and generating agent configuration files and node secrets.
Replicating changes due to administration and authentication activities.
Handling self-service requests.
Maintaining the most up-to-date AM database.
Related Articles
Synchronize Agent Authentication Records on the Primary Instance Number of Views Update the Primary Instance Hostname and IP Address on a Replica Instance Number of Views Getting the RSA backup files from the RSA Authentication Manager 8.x primary instance Number of Views Change the Hostname of a Primary or Replica Instance in Azure Number of Views Replica fails to attach to the RSA Authentication Manager 8.1 primary instance Number of Views
Trending Articles
RSA Authentication Manager Patch Updates Deploying RSA Authenticator 6.2.2 for Windows Using DISM RSA Authenticator for iOS and Android Administrator Guide - Mobile Lock RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Release Notes for RSA Authentication Manager 8.8
