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
How to operate RSA Federated Identity Manager (FIM) in specific time zone 9Number of Views A revocation request executes immediately in RSA Identity Governance and Lifecycle if the revocation date is defined beyon… 57Number of Views Invalid date format error in RSA Identity Governance & Lifecycle Salesforce collections 61Number of Views Setting NTP, date, time and time zone information for Authentication Manager 8.x running on SLES 15 40Number of Views Upgrade error occurs in RSA EnVision 4.1: 'Folder in Use' 26Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide