Known Browser Attribute for Authentication Conditions

Document created by RSA Information Design and Development on Jul 13, 2016Last modified by RSA Information Design and Development on Feb 9, 2018
Version 22Show Document
  • View in full screen mode

You can configure different authentication requirements for application access requests coming from known and unknown browsers.

When a usersuccessfully completes additional authentication using a method such as Approve or RSA SecurID, and clicks Remember This Browser, RSA SecurID Access "remembers" the browser and identifies it with the Known Browser attribute. If the user does not click Remember This Browser, the browser is not known.

Using the Known Browser attribute can simplify future authentication for users. For example, a rule set might require additional authentication for users with unknown browsers. After the user completes additional authentication successfully, the browser becomes known. The next time that user accesses the application with the same browser, the access policy might allow the user to skip additional authentication, or to use additional authentication with a lower assurance level.

Note:  Clicking Remember This Browser simplifies future authentication for a user only if you use the Known Browser attribute in an access policy.

If RSA SecurID Access cannot determine whether a browser is known, it handles the condition as if the browser is unknown. For example, if the condition is KNOWN BROWSER TRUE ALLOW ACCESS and the identity router cannot communicate with the Cloud Authentication Service to determine if the browser is known, RSA SecurID Access assumes the browser is unknown.

Browsers can reside on a mobile phone, tablet, desktop computer, or laptop. A user can remember one or more browsers running on a mobile device, regardless of whether the mobile device itself is registered.



Previous Topic:Access Policies
You are here
Table of Contents > Access Policies > Known Browser Attribute for Authentication Conditions