Why use RSA SecurID Access AD FS SAML integration rather than the RSA Authentication Agent for Microsoft AD FS
Originally Published: 2018-11-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 How to selectively challenge users and applications with RSA AD FS agent 1.x Number of Views Unable to authenticate on AD FS servers that are using different language than the default English-US when RSA Authenticat… Number of Views How to Synchronize Nested AD Group Users from an RSA SecurID Access Identity Source Number of Views Application Availability and Visibility Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?
