000035487 - RSA Adaptive Authentication (on Premise) - Device Registration Issues with CriOS in the User Agent

Document created by RSA Customer Support Employee on Dec 1, 2017
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000035487
Applies ToRSA Product Set: Adaptive Authentication (OnPrem)
RSA Version/Condition: 7.x
IssueA device information is not verified properly in RSA Adaptive Authentication (on Premise) when the elements Mozilla/5.0
(iPhone; CPU iPhone OS 8_1_2 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) CriOS/47.0.2526.107 Mobile/12B440
Safari/600.1.4 are present in User-Agent header.
The content of the header is passed to Adaptive Authentication service when a device is registered for a user.
It is supposed to be stored in Adaptive Authentication and compared with the same information when device is verified.
The testers noticed that this functionality does not work for iPhone devices. I ran some tests and found out that when “CriOS”
s present the device is never matched. With other values (“Chrome” for instance) this functionality works fine.

There is a bug in rsa.js file which is used for capturing and identifying device elements.

ResolutionThis is related to rsa.js functionality. We have to make changes to support this new User Agent. 
The fix is officially released as part of 7.3 P3.
WorkaroundAs a workaround deploy the attached latest release of the rsa.js file in the front end application.