YSoft SafeQ 6 - Release Notes Build 48

Infrastructure and other changes

Using Microsoft OAuth2 based authentication for accessing emails in Mobile Print Server

YSoft SafeQ now supports OAuth2 based authentication for accessing emails in the Mobile Print Server. (Microsoft announced that support for Basic Authentication using username and password will end later this year; the Mobile Print Server used Basic Authentication). From now on, administrators can choose to use the Mobile Print Server in OAuth mode. (SQC-1222)

Using Google OAuth2 based authentication for accessing emails in Mobile Print Server

YSoft SafeQ now supports OAuth2 based authentication for accessing emails in the Mobile Print Server. (Google announced the end of ability of less secure apps to access G Suite account data; the Mobile Print Server used this approach). From now on, administrators can choose to use the Mobile Print Server in OAuth mode. (SQC-2863)

Sharp - Support of new A4 devices from the Luna series

YSoft SafeQ Embedded Terminal can now be installed on Sharp A4 devices from the Luna series, a Lexmark OEM brand. Authentication, copy, print, scan workflows and device dependent accounting are supported. (SQC-2301)


Fixes and Improvements

Client Application, Terminals and User Interfaces

The native scan panel is enabled on Brother devices with embedded terminal. (SBT-1595)

The screen for card self-assignment requiring login and password now fits on Lexmark devices with small screens. (SBT-1008)

The Epson SDK was updated to version 1.10. (SQC-2510)

If HTTPS is enforced with 2nd Gen. Embedded Terminal, then images are downloaded over this protocol. (SBT-1544)

The desktop interface configuration file for the client application is now persisted to the user folder which should be accessible to the user at all times. (SBT-1327)

Information about 3D reference prints were added to the eDee terminal. (EDEE-2188)


Installation and Administration

Card numbers visible to a system administrator are now masked. The administrator can reveal them with the system property, maskCardNumber. (SBT-1004)

The description for the property, forceSecureDeviceDescription, in the management interface and documentation has been updated to reflect requirements for the OpenAPI version. (SBT-1543)

The description for the parameter, PIN-archivation-period, was improved in the management interface so it now refers to related properties. (SBT-136)

A server installation with an external MS SQL database is now able to properly connect to a database with NTLMv2. (SBT-1010)

Terminal server is able to start even if some port binding is not possible during the startup procedure. (SBT-1038)

Whenever an installer tries to create a database for IMS and fails, the installation process is now cancelled, giving user feedback with logs for obtaining more details. (SBT-1522)

Documentation has been extended with a description of the MS SQL server which hosts more product installations (e.g. production and test) which both use a MSSQL instance. (SBT-1080)

The user input field type for scanning workflows are now translated to the selected language. (SBT-1612)



Product extensions (formerly known as customizations)

The LPR client in the Job Routing Proxy (SWC-79) will not fail anymore if special characters are used in the print job title. Fixed was released in the Job Routing Proxy 3.6.3. (GSS-3085)

Customers who use YSoft SafeQ extensions should contact their Y Soft partner sales representative 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/extensions-store