Discrepancies in Device Information and User Agent in VIP Authentication Hub
search cancel

Discrepancies in Device Information and User Agent in VIP Authentication Hub

book

Article ID: 419354

calendar_today

Updated On:

Products

Symantec Identity Security Platform - IDSP (formerly VIP Authentication Hub)

Issue/Introduction

Running VIP Authentication Hub, in the database tables, the user agent data stored in the FP tables fpua field, the DEVICE_NAME column in the IA_DEVICE table, and the EVENT_USERAGENT column in the IA_EVENT table sometimes don't match.

This happens when login was done from a MobilePhone (Android 14).

To illustrate:

EVENT_USERAGENT= Mozilla/5.0 (Windows; U; Windows NT 6.0) AppleWebKit/536.2.1(KHTML, like Gecko) Chrome/28.0.819.0 Safari/536.2.1
FP= fpua=Mozilla/5.0 (Linux; Android 14; 2109119DG Build/UKQ1.240624.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/140.0.7339.51 Mobile Safari/537.36|Linux aarch64&fpsc=<value>|<value>|<value>|<value>|<value>&fpsw=&fppi=&fptz=2&fpln=<value>|||&fpcp=<value>&fpvc=&fpvs=2&fpch=&inc=0&fpts=<value>&fptg=<value>

Why are the EVENT_USERAGENT column and in FP (the fpua value) differ?

Environment

VIP Authentication Hub 3.4.4;

Cause

This is how the product works. 

The SDK Risk Web and the SDK Risk Android don't produce the same data (1)(2).

The SDK Risk Web gets its value only by the browser.

So, the data seen is as expected when using SDK Risk Web for a mobile flow.

Resolution

For the Mobile flow, use the SDK Risk Android (2).

Additional Information

  1. SDK for Risk Web

  2. SDK for Risk Android