browser-fingerprint
Reactive icon

Browser Fingerprint

Stable version 1.0.0 (Compatible with OutSystems 11)
Uploaded
 on 21 Jan (12 hours ago)
 by 
EONE TECHNOLOGIES PRIVATE LIMITED
0.0
 (0 ratings)
browser-fingerprint

Browser Fingerprint

Documentation
1.0.0

Configuration options

At the UI/block level, the component exposes checkboxes (or equivalent inputs) to select which data categories are included in the generated fingerprint.

Supported categories:

  • Browser Info: User agent, language, languages, platform, vendor, cookie enabled flag, do-not-track flag, online status.
  • System Info: CPU cores, device memory, timezone, timezone offset, touch support.
  • Screen Info: Screen width and height, available width and height, color depth, pixel depth, orientation, device pixel ratio.
  • Hardware Features: Max touch points, availability of Bluetooth, USB, and battery APIs.
  • Browser Features: Flags for localStorage, sessionStorage, IndexedDB, Web Workers, Service Workers, WebRTC, WebGL, Web Audio, Notifications, and Geolocation.
  • Font Detection: Detected font list (for example: Arial, Verdana, Times New Roman, etc.).
  • Plugin Detection: Installed plugins with name, description, and filename (e.g., PDF viewers).
  • Canvas Fingerprint: Stable hash value derived from a canvas rendering operation.
  • WebGL Fingerprint: Stable hash value derived from WebGL parameters.
  • Audio Fingerprint: Stable hash value derived from Web Audio fingerprinting.

Developers can bind these configuration options to inputs or keep them as default values in the block, depending on how much flexibility is required in each consumer screen.

How to use in OutSystems

Typical usage pattern in a consumer module:

  • Add the Browser Fingerprint block to a screen where a fingerprint is needed (e.g., login, sensitive operations, or device registration).
  • Expose input parameters for each configuration option if runtime control is required, or keep them fixed for consistent fingerprints.
  • Add a client action that calls the component’s “GenerateFingerprint” logic, usually bound to a button or executed on screen ready.
  • Capture the returned ID in local variables, then:
    • Store in an entity for audit or risk scoring.
    • Send to a REST API for device reputation checks.
    • Compare with previous fingerprints for the same user to detect suspicious device changes.