Check your application's documentation and/or the application's Integration Guide on RSA Link to see if it has a configuration option that will enforce access using only a single authentication source. Applications that support RADIUS or Relying Party or SAML single sign-on will typically prevent authentication by any other means, once those options are enabled. However, when HTTP Federation or Trusted Headers are used, there will probably not be a built-in means within an application that prevents bypass of the RSA Cloud Authentication Service.
An internal application or website protected by HTTP Federation or Trusted Headers can be limited to only accepting incoming connections from the RSA Identity Routers' proxy IP address, thereby denying access from any other source. This can be achieved with a firewall.
Related Articles
ASR fails to generate with 'ORA-31011: XML parsing failed' and 'LPX-00225: end-element tag "ROWSET" does not match start-e… 69Number of Views RSA Cloud Authentication Service End User Videos 14Number of Views How to bypass RSA SecurID multiple domain authentication page 51Number of Views How to bypass SSO for testing in RSA Identity Governance and Lifecycle 49Number of Views Skyhigh End User Remediation Flow - RSA Ready Implementation Guide 18Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process