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 Authentication context not added / Context validation failed errors authenticating with RSA Authentication MFA Agent for A… 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 How to Synchronize Nested AD Group Users from an RSA SecurID Access Identity Source Number of Views Error Facts are not available when trying to authenticate using the RSA Authentication Agent 2.0 for AD FS Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide "No decryption codes were found in the zip file" error when decrypting RSA SecurID tokens Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU
Don't see what you're looking for?
