Fixes and Improvements
Terminals, User Interfaces
Administrators can now configure the PIN entry keyboard on Xerox embedded terminals to default to a numeric layout instead of the standard alphanumeric one. The previous alphanumeric default remains unchanged unless this new setting is enabled. (SBT-5566)
A card swipe on an HP embedded terminal could be silently dropped if a stale session from before a device reboot or sleep was still recorded, requiring a second swipe to authenticate. The stale session is now detected correctly so the first swipe succeeds. (SBT-5545)
The default token lifetime for the desktop client required users to log in again every day even without any configuration changes. The defaults have been adjusted so a returning user is not prompted to log in as long as the client connects at least once within the configured refresh window. (SBT-5333)
Installation and Administration
The desktop client's main log file rotated too quickly by default, so important diagnostic information from a reported issue was often already gone by the time a support package could be collected. The default log size and retention have been increased. (SBT-5585)
Logging out of an OIDC session in the management interface failed on the identity provider's side because a relative redirect URL was sent where an absolute URL is required. The redirect URL sent during OIDC logout is now built correctly. (SBT-5578)
Updating an installation that uses an external MS SQL database without SQL encryption enabled could fail license validation with a missing-certificate error, blocking the update. This has been resolved. (SBT-5576)
The Secure LDAP Proxy service could crash on startup after a server reboot if its certificate could not be read, silently breaking user replication and authentication until it was manually restarted. An unreadable certificate is now handled gracefully and regenerated automatically. (SBT-5522)
When SAML was enabled for the end-user interface and a trust certificate entry (rather than only private-key entries) was present in its keystore, the end-user interface failed to start. Keystore entries are now handled correctly regardless of certificate type. (SBT-5348)
Collecting support information from the desktop client on macOS omitted several relevant log files after the client's background service had been restarted. Support packages now include the missing log files in this scenario. (SBT-5292)
A slow directory synchronization through the Secure LDAP Proxy could cause an unhandled error in the LDAP replicator, interrupting the synchronization. The replicator now handles this condition without failing. (SBT-5285)
Printing
The Microsoft Print Connector required an exact match to recognize a paper size and defaulted to A4 whenever the reported size didn't match exactly. Paper size matching now tolerates small rounding differences. (SBT-5509)
Scanning
On Brother devices, selecting the "One color" scan option did not map correctly when the option was also allowed to be changed by the user on the terminal, so scans were produced in color instead. The "One color" option is now mapped correctly in this case. (SBT-5540)
Scanning to a compressed PDF on an HP embedded terminal silently fell back to an uncompressed PDF instead, producing much larger files than expected. Compressed PDF scanning now works as configured. (SBT-5535)
Duplex scans on Konica Minolta devices could have every other page rotated 180°, because the binding position used for scanning was not configurable. An advanced scanning option is now available to set the binding position explicitly. (SBT-5574)
Saving a scan workflow with 240 or more assigned access roles in a single edit failed with a server error and no explanation. The interface now warns when too many roles are selected instead of failing silently. (SBT-5506)
Security Mitigation and Enhancements
Security improvements and fixes (SBT-5573, SBT-5559)
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