clientjs icon indicating copy to clipboard operation
clientjs copied to clipboard

Generating different fingerprint id for different browser issue

Open manojkrossark opened this issue 3 years ago • 4 comments

Hi Team,

We have installed the ClientJS package in react application and we have generated fingerprint IDs from different browsers (Chrome, Firefox, Edge). We have noticed that Client JS is generating different FingerPrint IDs for each browser.

Our use case is like, whenever users access our website, we wanted to identify from which device user is accessing our web application. If the user accessing it from the same device even with different browsers, we must have the same fingerprint ID returned even after years.

Could you please help us to resolve this issue?

manojkrossark avatar Jan 27 '22 09:01 manojkrossark

Hi Team, Thank you for the awesome ClientJS library. Its simple to integrate with ReactJS application and it generates same FingerprintID for Chrome incognito, Chrome Guest & Normal Chrome Browser.

But, When we generate FingerPrintID from different browser (Chrome, Firefox, Microsoft edge) on same device it generates different FingerPrintID for each Browsers.

We would like to get same FingerprintID (even for different browsers on same device) which uniquely identifies Device independent of browser. Could you please help us to resolve this issue?

iamvignesht avatar Feb 10 '22 12:02 iamvignesht

Hi, new here...

But, according to readme, the fingerprint is using, by default, de User Agent (that changes for every browser....)

Maybe, you need to do your own fingerprint, avoiding that parameter, using clientjs.getCustomFingerprint(...)

eleazan avatar Jun 15 '22 09:06 eleazan

Hello @Vignesh9291, How to implement clientjs with react js? Can you help me with this?

asif-jalil avatar Jan 30 '23 04:01 asif-jalil

Fingerprint libraries generate a different fingerprint ID for each browser because their purpose is identifying the browser, not the user who is using the browser.

While there is no complete guarantee that connections indicated as being made by the same browser were actually made by the same browser, figuring out that two different people are using the same browser or the same person is using two different browsers is harder.
Imagine I share my computer with a friend of mine, who uses a browser I do not usually use to connect to the same site. How could a JavaScript library understand if it is me connecting to the same site using two different browsers, or it is my friend who uses a different browser?

avpaderno avatar Apr 09 '23 17:04 avpaderno