Release Notes Build 74
Fixes and Improvements
Terminals, User Interfaces
Cloud terminal has successful feedback from the Terminal server when PIN method usage has been forbidden. (SBT-4174)
Installation and Administration
The default value of refreshPrintedPagesInterval has been changed to run every hour for the Rule-Based Engine condition "Total number of pages by user during current period" meaning critical information is no longer missing. (SBT-4184)
PIN generation succeeds in the Management User interface when requesting automatic PIN generation without an expiration date against a user. (SBT-4175)
ldapProcessDataAlternatively is enabled in system settings by default following the successful resolution to the issue whereby full LDAP replication was deleting users when a communication issue with the LDAP server occurred. (SBT-4172)
The steps for Truststore configuration for the end user interface using SAML are clearly defined and will therefore not create an error. (SBT-4150)
FSP client is now switching to offline mode following client restart of lost connection. (SBT-4140)
The user needs to swipe the card only once to authenticate after the application timeout. (SBT-4128)
When running the Dispatcher Paragon server installer with Windows Defender real-time protection enabled, the installation no longer hangs for more than an hour before it continues. (SBT-4089)
After enabling the separator page in Windows, the separator page should be printed and accounted to the same user who sent the print. (SBT3892)
In the management interface when a user is being synced from LDAP the LDAP replication log should not say that a user was added but should say that the user was ignored. (SBT-3870)
In the management interface when checking the roles of an existing user the 'Info' label will now reflect the correct color. (SBT-3144)
Security Mitigation and Enhancements
Spring4shell security vulnerability update with the removal of vulnerable libraries. Upgrade sprint framework to version 5.x. (SQC-6936)
Security has been enhanced with the requirement by default of the use of strong password criteria in the Management user interface. (SQC-6887)
In spring framework versions prior to 5.3.20+, 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attacks. In Y Soft services with vulnerable Spring versions (Management, Payment) have been updated to reflect versions 5.3.20+. (CVE-2022-22970/CVE-2022-22971) (SBT-4161)
"Authenticated Users" have read and execute rights for folders and subfolders/subfiles. (CVE-2021-31859) (SBT-4148)
Early Access Program
All notifications are displayed to the user on the SafeQ Client v3. user interface. (SBT-4157)
The authentication with STORED_USERNAME in SafeQ Client v3. is working correctly. (SBT-4151)
When the SafeQ Client v3. is unavailable the job will go to SPOOLER_ERROR. (SBT-4110)
YSoft SafeQ Client v3 is under the Early Access Program (YSQL6-049-0000; YSoft SafeQ Client v3; F_NEW_SQ6_CLIENT); see details about the program in Early Access Program. Client application use needs to be validated by a Y Soft Solution Consultant.
Other included change codes
SQC-7560, SQC-7549, SQC-7544, SQC-7543, SQC-7538, SQC-7535, SQC-7523, SQC-7522, SQC-7521, SQC-7486, SQC-7485, SQC-7484, SQC-7474, SQC-7473, SQC-7472, SQC-7470, SQC-7468, SQC-7460, SQC-7452, SQC-7447, SQC-7389, SQC-7380, SQC-7313, SQC-7269, SQC-7262, SQC-7257, SQC-7256, SQC-6940, SQC-6938, SQC-6397, SQC-5746, SQC-5170, SQC-4455, SQC-4441, SBT-4210, SBT-4205, SBT-4195, SBT-4180, SBT-4179, SBT-4178, SBT-4177, SBT-4176, SBT-4167, SBT-4164, SBT-4163, SBT-4143, SBT-4003, SBT-4000,
Product extensions (or customizations)
Customers who use YSoft SafeQ extensions or customizations should contact their Y Soft RSM or Customer Support Services for compatibility verification with the new Build. We recommend testing all extensions before applying a Build update into a production environment.
You can find additional information on Partner Portal: https://portal.ysoft.com/products/ysoft-safeq/extension-store/print-job-extension