Why use RSA SecurID Access AD FS SAML integration rather than the RSA Authentication Agent for Microsoft AD FS
Originally Published: 2018-11-06
Last Modified: 2023-10-06
Article Number
Applies To
Issue
- RSA Authentication Agent for Active Directory Federation Services (AD FS)
- SAML integration with the RSA Cloud Authentication Service
Resolution
However, there are some situations where SAML integration may be the better choice:
- Require SecurID as the primary authentication method and AD FS is running on Windows Server 2012 or 2016 (the agent can only provide additional/secondary authentication unless AD FS is running on Windows Server 2019 or later).
- Require FIDO token authentication (FIDO is not supported by the agent).
- Prefer not to install and maintain additional software on your AD FS server(s). The agent must be installed on each AD FS server in your server farm.
Related Articles
Troubleshooting RSA MFA Agent for Microsoft AD FS Number of Views Attributes are missing from the SAML response sent by the RSA SecurID Access Identity Router to Microsoft AD FS Number of Views RSA MFA Agent 3.0.3 for Microsoft AD FS Release Notes Number of Views The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn… Number of Views FIM - Unable to federate to SharePoint with ADFS and RSA FIM Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Governance & Lifecycle 8.0.0 Installation Guide Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6
Don't see what you're looking for?
