Global Connection Defaults (common.settings.js)

The common.settings.js file, located at C:\Program Files\Thinfinity\Workspace, defines a global configuration object named thinfinity_common. Its main purpose is to override and extend common settings for all Thinfinity® Workspace connections right before they are initiated.

This code acts as a general configuration template, applying its values to any connection a user opens. It functions as an overarching configuration layer, allowing an administrator or developer to centrally customize the default experience for all users.

It allows setting default values for parameters like newPage: false, which can be modified for the entire environment. For example, if you change fullScreen: false to fullScreen: true, all connections will attempt to start in full-screen mode by default, without the user having to select it each time.

This configuration modifies the user experience (UI/UX), as most of the options control the appearance and behavior of the user interface.

These definitions are applied partially. This means that if you remove a line from the object fullScreen: false, the application will simply use its own internal default for that option. Only the settings that are explicitly defined in this object are overridden.

Session-lifecycle behavior can also be controlled here. Setting autoDisconnectConnection: false prevents the automatic disconnection that would otherwise occur when a user’s login session is lost — useful for Thinfinity® VirtualUI applications where session continuity must survive authentication drops. For the equivalent property when configuring VirtualUI through app.js, see Change Browser Behavior Using ClientSettings.

Example: Watermark Visual Customization

This section is a single example — the manual doesn’t enumerate every parameter that can be added to common.settings.js. Most parameters ship as commented examples inside the file itself, so admins reading the file have the reference at hand. The watermark’s visual-appearance parameters are the exception: they don’t ship inline and must be added manually, so they’re documented here as the primary reference.

Adding a watermark: {...} object to thinfinity_common overrides the default rendering — any subset of properties can be set, and unset ones fall back to the default value. The sample below reproduces the shipped defaults, so it also doubles as a defaults reference.

watermark: {
    color: 'rgba(208, 192, 192, 0.35)',       // any CSS color; alpha controls how subtle it is
    font: {
        family: 'Arial, Helvetica, sans-serif',
        size: 16,                             // px size
        weight: 'normal',                     // 'normal' | 'bold' | 100..900
        style: 'normal'                       // 'normal' | 'italic'
    },
    angle: 45,                                // rotation of each mark, in degrees (diagonal)
    gap: { x: 300, y: 150 },                  // spacing between marks (px) — lower = more frequent
    layout: 'tiled',                          // 'tiled' (repeat) | 'single' (one centered mark)
    shadow: false,                            // subtle contrast halo (helps on busy/photo backgrounds)
    outlineColor: 'rgba(255, 255, 255, 0.45)',// any CSS color for the border stroke
    outlineWidth: 0                           // px thickness of the visible border; 0 = no outline
}

The Show watermark toggle and Watermark text template that control per-profile activation and content live in each Access Profile’s User Experience settings — see, for example, RDC User Experience Settings.

Tamper Guard

The watermark overlay is actively guarded in the browser. If a user removes, hides, or restyles it to be invisible — for example, through the browser’s developer tools — the overlay is re-asserted automatically. Persistent tampering within a short window is treated as a deliberate attack and escalates to a configured fail-closed action; by default the escalation is purely a restore, but integrators embedding the client can wire it to disconnect the session instead.

The guard’s parameters (watchdog interval, escalation threshold, and action) are not exposed to common.settings.js, since they govern behavior rather than appearance. The guard is on by default and does not require any configuration.

Where the Overlay Is Delivered

The watermark configuration is carried in the connect-result that the gateway sends to the browser, so the overlay reaches every connected browser — including sessions that use an anonymous shared-key (_skey) link. There is no separate opt-in path for anonymous access. The watermark text is resolved from the session owner, not from each viewer: on an anonymous shared-key link, $(LOGIN_USER) shows the name of the user who owns the session. A watermark captured from a shared-key viewer identifies the session, not the person watching it.