Release Notes 1.2.1.2
Introduction
This is the first widely available version of a reworked Web Terminal Client user interface.
This new version of the client has been designed intentionally to preserve the user interface (UI) of version 1.1. However, it has been optimized for speed and to reduce code maintenance overhead, enabling the development of new features more efficiently.
Several key areas have been specifically updated:
- The graphical keyboard re-mapper has been refreshed to improve its user-friendliness.
- The screen payload transferred between the client and the web server has been significantly accelerated.
Metadata
This release documentation version 1.0.
| Release | 1.2.1.2 |
|---|---|
| Release date | 2024-09-24 |
| Release type | Full release |
| Future | Main branch release |
| Server version | 1.2.1.2+1.2.1.2-b539d3d |
| Log Server version | 1.2.1.2+1.2.1.2-35acd8c |
| HostScreen Server version | 1.2.1.2+1.2.1.2-1ae65508 |
| Web Terminal Hub version | 1.2.1.2+1.2.1.2-5d2e287 |
| Web Terminal Client version | 1.2.1.2+1.2.1.2-a24f571 |
| Management Console | 1.2.1.2+1.2.1.2-ff5f4f5 |
| Log Viewer | 1.2.1.2+1.2.1.2-dd17df5 |
.NET Platform
| .NET Release | 8.0.8 |
|---|---|
| .NET Runtime | 8.0.8 |
| ASP.NET Core Runtime | 8.0.8 |
| Notable changes | Link |
Web Terminal Client Renderer File Names (checksum)
Location: Program Files\Flynet\Jubilant\WebTerminal\web
| renderer.0ad204807320449b6767.js | renderer.191ab12d65cee0117db4.js |
| renderer.1493df2d2054c22ebfdf.js | renderer.05181b0626c76a4becc8.js |
| renderer.ae24acce9733b5a5256d.js | renderer.b7b6e9b6608bdd597d1a.js |
| renderer.b9fc01e794912c58bbcd.js | renderer.cb7ab0a72ff46265163d.js |
| renderer.e8d6bb3353755ffa43ef.js |
Upgrade Recommendations
This release does is not required to fix any known security issues.
This release does not include any general high importance fixes for Jubilant. Please review the fix section below to see if there are any specific fixes that are relevant.
Security Notes
This release does is not required to fix any known security issues.
.NET Security
.NET 8.0.8 is used this release of Jubilant that includes security updates. Maximum severity: Important. However, these vulnerabilities are not surfaced in Jubilant. Please see these notable changes.
Node and Nuget Packages Security
This release contains no known critical or high severity Node vulnerabilities.
A single moderate severity issue is not surfaced in Jubilant. This package will be updated in a near future release.
A single low severity issue is not surfaced in Jubilant. This package will be updated in a near future release.
High Importance Fix Notes
This release does not include any general high importance fixes for Jubilant. Please review the fix section below to see if there are any specific fixes that are relevant.
In this Release
New
| ID | Protocols | Description |
|---|---|---|
| WTC.296 | All | Terminal Screen can be toggled between Stretch-to-Fit and maintain-aspect-ratio modes. |
| WTC.300 | All | The Web Terminal Client logs metrics and diagnostics. |
| WTC.302 | All | Browser compression is applied to screen interaction communications. |
| WTC.305 | All | CTRL and ALT modifiers enabled on Virtual Keyboard. |
| WTC.320 | All | Apple Safari users notified of local clear-text history storage on non-HTTPS connections. |
Fix
| ID | Protocols | Description |
|---|---|---|
| WTC.306 | All | Fixed Caps Lock to only capitalize letters and not shift numbers and symbols. |
| WTC.309 | All | Fixed CTRL + C keypress for iOS-based devices. |
| WTC.311 | All | Fixed incorrect screen history font for Safari (and other WebKit-based browsers) on iOS-based devices. |
| WTC.314 | All | Fixed screen history failing over non-HTTPS. |
Security
| ID | Protocols | Description |
|---|---|---|
| .Net 8.0.8 | All | See .Net Security Notes. |
Change Notes
WTC.296 - Terminal Screen can be toggled between Stretch-to-Fit and maintain-aspect-ratio modes
It is now possible to toggle the aspect-ratio mode for the terminal screen.
Stretch to Fit true |
Stretch to Fit false |
|---|---|
 |
 |
When Stretch to Fit is enabled (true), the terminal screen will be stretched (scaled) to fit all available browser space.
When Stretch to Fit is disabled (false), the terminal screen will use the maximum web browser space available without distorting the font ratio.
Administrators can set the default with an option in settings.json. This by default is located in the C:\Program Files\Flynet\Jubilant\WebTerminal\web\settings folder.
{
"StretchToFit": true
}
Users can set their own preference by using the Stretch To Fit option in the Web Terminal General Settings.
WTC.300 - The Web Terminal Client logs metrics and diagnostics
The Web Terminal Client can now log diagnostics the server-side session log and JavaScript console.
Settings are found in WebTerminalSettings.json. By default, these are found in C:\ProgramData\Flynet\Jubilant\WebTerminal\web\hub.
{
"ClientLogSettings": {
"OverrideServerLogLevel": true,
"ClientLogLevel": "Error",
"ClientLogTarget": "Server"
}
}
OverrideServerLogLevel
If this is set to false, the log level for client logging will be the same as set in FJManage -> Logging Server -> Log Level.
If this is set to true, the log level is set using the ClientLogLevel setting in this configuration file.
By default, this setting is true.
ClientLogLevel
The ClientLogLevel is only applied if OverrideServerLogLevel is set to true.
If applied, this setting sets the Client Log level. Value values are:
- Trace
- Debug
- Information
- Warning
- Error
- Critical
- None
ClientLogTarget
Value for ClientLogTarget are:
- Server - Log into the server-side (Correlation ID) session log.
- Local - Log into the JavaScript console.
- Both - Log into the server-side (Correlation ID) session log and the JavaScript console.
WTC.302 - Browser compression is applied to screen interaction communications
By default, Jubilant uses high performance binary blobs for screen and key press transmission between the web browser and the server.
As network bandwidth is more precious (especially for organizations working over mobile / cell or public infrastructure) than browser accelerated compression time, compression / decompression has been enabled by default.
Compression is only applicable to binary MessagePack messaging, not JSON messaging. MessagePack is the default.
The settings for controlling compression is found in WebTerminalSettings.json. By default, this file will be located in C:\ProgramData\Flynet\Jubilant\WebTerminal\web\hub.
{
"ClientCompression": "GZip",
}
The valid values for ClientCompression are:
- None - do not apply compression.
- GZip - apply GZip compression.
WTC.305 - CTRL and ALT modifiers enabled on Virtual Keyboard
CTRL and ALT keys on a Virtual Keyboard now function as modifiers triggering any re-mapped action.
WTC.320 - Apple Safari users notified of local clear-text history storage on non-HTTPS connections
Apple Safari blocks access to the cryptography API if a web site is being accessed with a non-HTTPS connection. Users are informed that their screen history is being written to local user storage unencrypted.
If other browsers block access to the API, this feature will also triggered.
If storing history text in unencrypted form is against an organization's policy, HTTPS must be enabled for the Jubilant web site.
WTC.306 - Fixed Caps Lock to only capitalize letters and not shift numbers and symbols
In previous builds of Jubilant the Caps Lock key on the Virtual Keyboard functioned as Shift Lock. This modified numeric and character keys to their shifted form.
This build fixes this issue by implementing true Caps Lock, only capitalizing alpha keys and leaving numeric and character keys unshifted.
WTC.309 - Fixed CTRL + C keypress for iOS-based devices
A known bug in Apple iOS-based devices sends the incorrect keycode to the browser when pressing CTRL + C.
This Apple bug is taken into account and is worked around in this build.
WTC.311 - Fixed incorrect screen history font for Safari (and other WebKit-based browsers) on iOS-based devices
In previous builds of Jubilant, a font was not correctly applied to the screen history. This is resolved in this build.
WTC.314 - Fixed screen history failing over non-HTTPS
In previous builds of Jubilant, screen history would fail if the cryptography API was not available. In this build, the history falls back to non-encrypted storage.
Also see WTC.320 - Apple Safari users notified of local clear-text history storage on non-HTTPS connections.
Installation
Fresh Install
Please see the Jubilant Admin Manual for Fresh Install Instructions.
Upgrade
Note
Please note the specials steps below if upgrading from a 1.0.x build to a 1.1.x or later build.
If upgrading from Jubilant 1.0.x to 1.1.x extra steps must be carried out before and after the install steps below.
Upgrade is carried out using Jubilant scripts.
- Unzip the installer into a folder.
- Close any web browsers.
- Close any Services windows.
- Open PowerShell ISE as Administrator.
- In the PowerShell ISE open the Jubilant PowerShell script: "JubilantUpdate.ps1".
- Run the required script by pressing the green play / run script button on the toolbar.
- The upgrade of Jubilant is complete.
If this is an upgrade from Jubilant 1.0.x to 1.1.x, make sure the after install steps are also completed.
Version Validation
Find out how to validate the installed version.