v2.14 Release: Optional client fingerprinting

[hoodoer]

Schema change.

Thought this would take longer, but it was actually easy to add. A small hash can be calculated based on various attributes of a JS-Tap client. While certainly not a "unique" identifier, it can often help identify a unique user and their browser on a specific system. This can help find JS-Tap clients who are actually the same user.

You can enable the fingerprint calculation in the JS-Tap payload configuration, and then if you want to show the fingerprint value in the JS-Tap portal UI simply enable it in the App Settings modal.

The client filter search references the fingerprint element, so you can copy/paste a fingerprint value into the filter search and show all clients with the same fingerprint.

[hoodoer]

Hmm, this might be buggy actually. I just saw some weirdness that went away when I disabled fingerprinting, so this might need some work.