Disable a User for Risk-Based Authentication
Disabling a user for risk-based authentication (RBA) prevents the user from accessing RBA-protected resources. The system retains the user's RBA-related data, including the user's authentication history and device history. (Devices remain in the user device history according to the device administration settings in the RBA policy.)
Note: If the RBA policy allows users to become automatically enabled for RBA, then the user can become re-enabled for RBA. For more information, see Methods for Enabling Users for Risk-Based Authentication.
Procedure
In the Security Console, click Authentication > Risk-Based Authentication > Manage Enabled Users.
Use the search fields to find the user that you want to disable for RBA.
Click the user that you want to disable for RBA, and select Risk-Based Authentication.
Under RBA Settings, deselect Enable user for RBA.
Click Save.
Related Articles
Enable Users Automatically for Risk-Based Authentication 6Number of Views Risk-Based Authentication 3Number of Views Enable Users Manually for Risk-Based Authentication 5Number of Views Device History for Risk-Based Authentication 6Number of Views View Risk-Based Authentication Settings for a User 6Number of Views
Trending Articles
Change Requests stuck in the AFX Fulfillment Handler Workflow Node and Workflows Stalled in RSA Identity Governance & Life… Collector Stuck in Data Collection Phase with "Sent Request to Agent Hosting the Collector" RSA Authentication Manager 8.9 Patches and Hotfixes Readme How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle