Release Notes 1.6.0.9
Important This Version Requires .NET 10.0
This version REQUIRES .NET 10.0, please update your .NET Hosting Bundle to the latest .NET 10.0 version BEFORE installing or updating to this LTS.
You can download the .NET 10.0 Hosting Bundle here
Once you have updated to the .NET 10.0 Hosting Bundle, you can uninstall the .NET 8.0 Hosting Bundle so long as you do not have any other software installed which relies upon it.
Metadata
This release documentation version 1.0.
| Release | 1.6.0.9 |
|---|---|
| Release date | 2026-08-31 |
| Release type | Full release |
| Future | Main branch release |
| Server version | 1.6.0.9+v1.6.0.9-LTS-3fcaad9 |
| Log Server version | 1.6.0.9+v1.6.0.9-LTS-1357f75 |
| HostScreen Server version | 1.6.0.9+v1.6.0.9-LTS-8337ee5 |
| Web Terminal Hub version | 1.6.0.9+v1.6.0.9-LTS-c8d98cc |
| Web Terminal Client version | 1.6.0.9+v1.6.0.9-LTS-f1e1549 |
| Management Console | 1.6.0.9+v1.6.0.9-LTS-988eb14 |
| Log Viewer | 1.6.0.9+v1.6.0.9-LTS-a59d6d6 |
.NET Platform
| .NET Release | 10.0.11 |
|---|---|
| .NET Runtime | 10.0.11 |
| ASP.NET Core Runtime | 10.0.11 |
| Notable changes | Link |
Web Terminal Client Renderer File Names (checksum)
Location: Program Files\Flynet\Jubilant\WebTerminal\web
| 139.80bc5c13b34659596444.js | 175.0d3b381862e6de72424e.js |
| 193.b2d3b9069542c3e95ab2.js | 195.007ddb02397f3a82986f.js |
| 264.3f70d2733065bb50ca31.js | 312.1759754b6454de7a9c2c.js |
| 348.82112b0de69fee4f33d5.js | 352.47a2dc0f65bc3a0eb6a5.js |
| 637.a2b47361b46b309e5ace.js | 945.3787e3723abfa2bea690.js |
| 952.87644a150f8732ef16f0.js | loader.25292ba42daca28a138e.js |
| main.fbb7dd84e7866d9d49f4.js |
Upgrade Recommendations
This release is recommended for all users. The upgrade to .NET 10 includes many security and performance updates.
Security Notes
This release contains many security updates.
.NET Security
.NET 10.0.11 used in this release of Jubilant includes security updates. Maximum severity: High. However, these vulnerabilities are not surfaced in Jubilant. Please see these notable changes.
Node and Nuget Packages Security
None
High Importance Fix Notes
None
In this Release
Preview
The preview version of Automations (macros) first available in 1.3.1.3 continues to be improved. If you are interested in working with the preview, please contact support@flynet.email for more information.
New
.NET 10. This version introduces support for .NET 10
Fixed
| ID | Protocols | Description |
|---|---|---|
| HSS.120 | ALL | Add code page 1146 Uk with Euro |
| HSS.122 | ALL | Fix security issues with ind$file upload |
| HSS.124 | 3270 | Fix 3270 HighlightQueryReply is incorrect |
| WTA.97 | ALL | Add the ability to use custom fonts |
| WTA.98 | ALL | Support for OIDC refresh tokens has been added |
| WTA.101 | ALL | Add support for OIDC ACR values |
| WTA.104 | ALL | Add support for mapping unique JSON keys in OIDC |
| WTA.105 | ALL | Add support for removal of ASP.NET cookies when user is not authorized |
| WTA.108 | ALL | Add the option to require authentication to access the help |
| WTA.111 | ALL | Add the ability to control whether all inbound OIDC claims are mapped or not |
| WTA.112 | ALL | Add server-side storage of OIDC tokens |
| WTA.114 | ALL | Fix security issues with ind$file upload |
| WTC.508 | ALL | Fix extremely fast input to the client can be lost |
| WTC.512 | ALL | Fix server storage not updated when reset buttons are used |
| WTC.514 | ALL | Add the option to remap opening the browser print dialog to the keyboard mapper |
| WTC.516 | ALL | Add default foreground and background colors to the color mapper |
| WTC.517 | ALL | Fix security vulnerabilities identified by security testing |
| WTC.518 | ALL | Add OIDC reconnection functionality |
| WTC.518 | ALL | Fix printer client ping timeout overrides display value |
| WTC.523 | ALL | Fix ERASEINPUT only clears a single line not a multi-line |
| WTC.526 | ALL | Fix onUnload event being deprecated in several browsers |
| WTC.532 | ALL | Fix pasting a double-byte character into an input field breaks the field |
| WTC.537 | ALL | JSON mode client connections break server storage |
| WTC.541 | ALL | Fix an error is preventing saving of color schemes |
| WTC.542 | ALL | Fix validation of server stored settings breaks with some settings values |
| MCC.85 | ALL | Fix save button behavior on host definition edit screen is inconsistent |
| MCC.87 | ALL | Fix some fields on the Global Settings page of the Management Console return the wrong data type |
| MCC.88 | ALL | Add success/failure toasts when the hub is called |
| MCC.89 | ALL | Fix updating logging settings appears tom be broken |
Known Issues
| ID | Protocols | Description |
|---|---|---|
| WTC.429 | ALL | On-screen keyboard on small screen devices |
| WTC.492 | ALL | Screen size calculations are slightly off |
Security
| ID | Protocols | Description |
|---|---|---|
| .Net 10.0.11 | All | See .Net Security Notes. |
Change Notes
HSS.120 Add code page 1146 UK with Euro
Code page 1146 UK with Euro is now available to be selected on host definitions.
HSS.122 Fix security issues with ind$file upload
Security testing revealed possible security issues with ind$file upload, these have been resolved in this release.
HSS.124 Fix 3270 HighlightQueryReply is incorrect
The reply to a host highlight query was incorrect. This has been resolved in this release.
WTA.97 Add the ability to use custom fonts
Font files placed into the Flynet\Jubilant\WebTerminal\web\fonts are available for use in the client. See the readme file in the fonts folder for more details.
WTA.98 Add support for OIDC refresh tokens
Note: currently the refresh token support will not work if communication with the client utilizes web sockets. This limitation will be removed in a future release.
A number of new settings have been added to the OIDC settings in WebTerminalSettings.json to support token refresh:
- AuthorizationHeaderStyle (default: Rfc6749, option: Rfc2617) sets the 'style' of the authorization header. The default is correct for most systems, Rfc2617 is for older systems.
- ClientCredentialStyle (default: AuthorizationHeader, option: PostBody) sets the 'style' of the credentials passed. The default is correct for most systems, though some may require PostBody.
- RefreshTokenThresholdSeconds (default: 0) when a request is received by the server, if its token has less than this number of seconds before it expires then an attempt will be made to refresh it.
- TokenRefreshUrl (default: empty string) the URL to call to refresh the token.
- UseRefreshToken (default: false) set to true to enable token refresh on the server.
Consult your OIDC provider's documentation to check the appropriate values of these settings for your server.
Note: if UseRefreshToken = true, then TokenRefreshUrl must have a value and RefreshTokenThresholdSeconds must be > 0 or you will get an error in the 5007 log and token refresh will not be enabled.
WTA.101 Add support for OIDC ACR values
A new property, AcrValues (default: an empty string), has been added to the OIDC settings in WebTerminalSettings.json. Set this property to the required ACR values to pass them on login.
WTA.104 Add support for mapping unique JSON keys in OIDC
A new property, UniqueJsonKeys (default: an empty collection), has been added to the OIDC settings in WebTerminalSettings.json. Entries in this collection have the following structure:
"UniqueJsonKeys": [
{
"Item1": "<claim_type>",
"Item2": "<json_key>"
}
],
Where claim_type is the type of the claim being mapped to and json_key is the key in the OIDC claims which should be mapped to the given claim_type.
WTA.105 Add support for removal of ASP.NET cookies when user is not authorized
Under certain circumstances a user with existing ASP.NET cookies may have difficulty logging in due to header size limits. A new property, RemoveAspNetCookiesWhenNotAuthenticated (default: false), can be added to the appsettings.json file in Flynet\Jubilant\WebTerminal\web\hub and set to true to remove these cookies for an unauthorized user.
WTA.108 Add the option to require authentication to access the help
Security testing revealed that the help can be accessed without authentication. To resolve this issue a new property, RequireAuthForHelpAccess (default: false), has been added in WebTerminalSettings.json. Setting this property to true will require users to be authenticated before accessing the help.
The new location for the help is:
C:\ProgramData\Flynet\Jubilant\Help
If you currently have custom help files then the JubilantUpdate.ps1 will move them for you but only if you add a marker file, preserve.txt, to your existing help in Flynet\Jubilant\WebTerminal\web\help.
Currently only OIDC authentication is supported, other authentication methods will be supported in future releases.
WTA.111 Add the ability to control whether all inbound OIDC claims are mapped or not
In the situation that a user has a large number of claims, mapping all claims by default can cause excessively large ASP.NET cookies leading to issues with header sizes. A new property, MapInboundClaims (default: true), has been added to the OIDC settings in WebTerminalSettings.json. If you are experiencing issues with header sizes, setting this to false may resolve the issue.
WTA.112 Add server-side storage of OIDC tokens
In the situation that a user has many claims that must be mapped, a users OIDC tokens can become so large that the ASP.NET cookie's size exceeds header limits. To deal with this situation a new property, SaveTokensServerSide (default: false), has been added to the OIDC settings in WebTerminalSettings.json. Setting this to true may resolve issues with excessively large cookies.
WTA.114 Fix security issues with ind$file upload
Security testing revealed possible security issues with ind$file upload, these have been resolved in this release.
WTC.508 Fix extremely fast input to the client can be lost
There was an issue where extremely fast input (e.g. barcode scanners) could be lost by the client. This has been resolved in this release.
WTC.512 Fix server storage not updated when reset buttons are used
There was an issue where resetting the various client settings did not update settings stored in server storage. This has been resolved in this release.
WTC.514 Add the option to remap opening the browser print dialog to the keyboard mapper
An action has been added to the keyboard mapper to allow the action of opening the browser print dialog to be remapped.
WTC.516 Add default foreground and background colors to the color mapper
Entries have been added to the color mapper to allow re-mapping of the default foreground and background colors.
WTC.517 Fix security vulnerabilities identified by security testing
Security testing revealed a number of potential issues. These have all been resolved in this release.
WTC.518 Add OIDC reconnection functionality
Functionality has been added to allow the client to re-authenticate via OIDC and then re-connect to an existing session.
WTC.521 Fix printer client ping timeout overrides display value
There was an issue where the client ping timeout on an associated printer definition overrode the timeout originally set on the display. This has been resolved in this release.
WTC.523 Fix ERASEINPUT only clears a single line not a multi-line
There was an issue where the ERASEINPUT client action only cleared a single line of a multi-line input. This has been resolved in this release.
WTC.526 Fix onUnload event being deprecated in several browsers
The onUnload event has been deprecated by some browsers. The Jubilant client no longer makes use of thi event.
WTC.532 Fix pasting a double-byte character into an input field breaks the field
There was an issue where pasting text containing one or more double-byte characters into an input field broke the field. The current resolution for this issue is to disallow pasting of double-byte characters with a warning instructing the user to ues the IME input instead.
WTC.537 JSON mode client connections break server storage
There was an issue where switch client connections from Message Pack to JSON would cause server storage of client settings to fail. This has been resolved in this release
WTC.541 Fix an error is preventing saving of color schemes
There was an issue where a client error prevented the user from saving color schemes. This has been resolved in this release.
WTC.542 Fix validation of server stored settings breaks with some settings values
An issues existed where the validation of settings stored in server storage would fail. This has been fixed in this release.
MCC.85 Fix save button behavior on host definition edit screen is inconsistent
There was an issue that caused inconsistent behavior for the save button on the host definition edit screen. This has been resolved in this release.
MCC.87 Fix some fields on the Global Settings page of the Management Console return the wrong data type
There was an issue where some fields on the Global Settings page of the Management Console returned the wrong data type to the server. This has been resolved in this release.
MCC.88 Add success/failure toasts when the hub is called
Success/failure toasts have been added to several hub calls that were missing them.
MCC.89 Fix updating logging settings appears tom be broken
There was an issue where updating the logging settings via the Management Console gave no feedback and did not update the settings on the server. This has been resolved in this release.
WTC.429 On-screen keyboard on small screen devices
On small screen devices the on-screen keyboard can be difficult to use. The work around is to define a new keyboard layout and select it via the settings.
WTC.492 Screen size calculations are slightly off
Under certain, rare, circumstances an issue with screen size calculations can cause the top line of the screen to be partly or wholly obscured. This usually occurs when the host changes the screen resolution. The work around is either to turn on stretch to fit in the settings menu or to resize the browser window, changing its width until the top line is visible.
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 version before 1.6.x.
If upgrading from a version of before v1.6.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 before 1.6.x, make sure the after install steps are also completed.
Version Validation
Find out how to validate the installed version.