Skip to content

Some trials to uniquely identify a device using a Web Application

Notifications You must be signed in to change notification settings

pcbl/DeviceID_WebApp

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 

Repository files navigation

DeviceID_WebApp

Some trials to uniquely identify a device using a Web Application (https://stackoverflow.com/questions/63506374/unique-deviceid-on-javascript-web-applicationangular-react)

Basically while running on a Browser sandbox, an angular application would have some hard time to uniquely identify a device.

With that in mind, this POC makes 2 Approaches:

  • Obtain a fingerprint via Fingerprintjs2: https://valve.github.io/fingerprintjs2/

    • FingerptintJS tries to generate a unique fingerprint, given the configuration of the browser by "comnbining" this features into a hash...
    • Pros:
      • Can be shared among apps: If you have multiple angular apps and you get the fingerprit, you will get the same id, without any need to save cookies or anything like that
      • Even if you clear the Browser history, you will get same fingerprint(as long no device settings were modified)
    • Cons
      • If you have two devices that are the same, configured on same way, you could get the same fingerprint
      • Browser dependent: If you open a different browser(Chrome, Safari, ...), you will get different fingerprints
      • As soon as the device has a setting changed(language, resolution,...) you will get another fingerprint
  • Generate a GUID ourselves and save it to a cookie

    • There are some ways to create a GUID from javascript. As soon you generated it, just save it to a cookie
    • Pros:
      • Not many...
    • Cons:
      • Browser dependent: If you open a different browser(Chrome, Safari, ...), you will get different Ids as you save them to a cookie
      • Cannot be easily shared accross apps: Unlike fingerprintJs, if you have multiple angular apps you would need some iframe solution to share a cookiw, which is uggly and can be tricky to do...
      • Cookie dependent: If you clean your browser cache, or use an anonymous window, you will get different IDs

So the idea would be to combine one of the approaches above(Fingerprint would be a good one) with the IP of the device, which we could get form the Backend... It would still not be waterproof as we can get same IPs when coming from a proxy, but would be one step better...

Another approach would be to use Cordova/Ionic to get the device ID and forward it to the application, but that would demand a high effort to publish one app just for that...

To run this POC:

After you cone the repo:

  1. Open the https://github.com/pcbl/DeviceID_WebApp/blob/master/Backend/DeviceIdentifier.sln Solution on Visual Studio and run it

  2. On a command prompt window, go to the Frontend directory and run the following commands:

    • npm install (might take some minues, go on and grab your coffee)

    • ng serve

  3. Once ng serve compiled and started the Angular server, navigate to http://localhost:4200

  4. If you click on the Request Button, you will see the device Information that you might get from the server(including the IP)

About

Some trials to uniquely identify a device using a Web Application

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published