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
A revocation request executes immediately in RSA Identity Governance and Lifecycle if the revocation date is defined beyon… 53Number of Views Invalid date format error in RSA Identity Governance & Lifecycle Salesforce collections 59Number of Views How to modify syslog date format on RSA Authentication manager 8.4 and up 100Number of Views How to operate RSA Federated Identity Manager (FIM) in specific time zone 9Number of Views Options for manage-securid-authenticate-app-provisioning 2Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Download OTP Token Seed Files from myRSA