Configure Web-Based Application Logon Pages for Risk-Based Authentication
To log on to an application that is protected by risk-based authentication (RBA), the users must provide their credentials to the application logon page that is modified using the RBA integration script. The RBA integration script redirects users to RSA AM.
Procedure
In the Security Console, select Access > Authentication Agents > Manage Existing.
Click the appropriate web-based application agent, and select View.
Under Risk-Based Authentication (RBA) Settings, click Go to Download Page.
If you are using a web tier, confirm that the values for the following are correct:
Virtual Hostname
Virtual Host Port
Authentication Agent
In the Agent Type drop-down list, select your web-based application.
Click Download File.
To add the script to the logon page for your web-based application, follow the instructions provided in the RSA implementation guide for your web-based application.
After you finish
Enable users for RBA. For instructions, see Enable Users Automatically for Risk-Based Authentication.
Related Articles
Custom Solutions for Web-Based Applications for Risk-Based Authentication 11Number of Views Change Requests cancelled by Escalation Workflows progress to Fulfillment instead of getting cancelled in RSA Identity Gov… 131Number of Views How to define a Request Button in RSA Identity Governance & Lifecycle to allow single or multiple user selection based on … 28Number of Views Do the RSA SecurID Access mobile apps support the Time-based One-time Password Algorithm (TOTP)? 192Number of Views RSA Governance & Lifecycle 8.0 Patch 06 Release Notes 298Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…