RSA Authentication Manager 8.4 responds to authentication requests coming from RSA Authentication Agent 2.0 for Active Directory Federation Services (AD FS) with a delay of 20 seconds
Originally Published: 2019-09-12
Last Modified: 2022-06-20
Article Number
Applies To
RSA Product/Service Type: Authentication Agent for Active Directory Federation Services (AD FS)
RSA Version/Condition: 2.0
Issue
Cause
Resolution
Workaround
- Define the agent within the Security Console with a fully qualified host name (Access > Authentication Agent > Manage Existing or Add New).
- Make sure that the agent is resolvable in the page by clicking Resolve IP or Resolve Hostname.
- Verify that the hostname is resolved by DNS using nslookup <hostname> via command line.
- Confirm that the agent name matches with the actual name of the machine with the RSA Authentication Agent 2.0 for Active Directory Federation Services (AD FS) installed.
Related Articles
Converting a NCLOB to a VARCHAR2 in TO_DATE after error ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conve… 112Number of Views RSA Authentication Agent 1.0.1 for Active Directory Federation Services (AD FS) sends domain\samAccountName instead of UPN… 79Number of Views RSA Web Threat Detection - Delayed Transactions Not in Shard File for the Correct Hour 10Number of Views Patch or upgrade running long in step ACM-105090.sql in RSA Identity Governance & Lifecycle 91Number of Views How to selectively challenge users and applications with RSA AD FS agent 1.x 130Number 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
Don't see what you're looking for?