-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generating different fingerprint id for different browser issue #137
Comments
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? |
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(...) |
Hello @Vignesh9291, |
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. |
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?
The text was updated successfully, but these errors were encountered: