Accurate System Date and Time Settings
RSA Authentication Manager requires accurate date and time settings for replication and authentication. If the token clock and the RSA Authentication Manager system clock do not match, the generated tokencodes will not match, and authentication attempts can fail. Specifying a Network Time Protocol (NTP) server for the instance prevents replication and authentication issues that are caused by clock drift.
Note: An NTP server is required in a replicated deployment. RSA requires that all RSA Authentication Manager instances have their time synchronized to an NTP server.
If you do not specify an NTP server in RSA Authentication Manager, the virtual appliance uses the date and time provided by the physical machine hosting the virtual appliance. In this situation, the physical machine hosting the virtual appliance should be configured to obtain accurate date and time information from an NTP server.
Make sure that you have the hostname or IP address of an NTP server before running Quick Setup.
Related Tasks
Related Articles
Why automatically generated revocation requests do not add back revoked requests on a revocation date in RSA Identity Gove… 31Number of Views Unable to reach one of the appliances in a cluster intermittently 29Number of Views Zoho Mail - SAML My Page SSO Configuration - RSA Ready Implementation Guide 2Number of Views How to modify syslog date format on RSA Authentication manager 8.4 and up 97Number of Views Status pages very slow on one of the two appliances in a cluster 19Number of Views
Trending Articles
Connection fails to Cloud Authentication Service when connecting through a proxy server from RSA Authentication Manager to… Downloading RSA Authentication Manager license files or RSA Software token seed records Unable to login to RSA Authentication Manager Security Console as super admin RSA Authentication Manager 8.9 Release Notes (January 2026) How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device