PaperCut NG 26.0 release history

New Features

SAML 2.0 Authentication

• This feature introduces SAML 2.0 for single-sign-on support (SSO), enabling PaperCut NG/MF to integrate with external Identity Providers (IdPs) such as Microsoft Entra ID, Okta, and Ping Federate. This allows System Administrators to provide a consistent login flow and leverage IdP security features, including Multi-Factor Authentication (MFA), across all PaperCut touchpoints to significantly enhance environment security. [PO-4158], [PO-638]

Unified Authentication

• We have redesigned the authentication architecture to provide a persistent “sign-in once” experience across the login web interfaces, Print Deploy, and the User Client. This reduces login fatigue for users and simplifies identity management for System Administrators by maintaining a single authenticated session across the platform.

Fixes

• Fixed an issue where logging out of the Mobile Print Release or Web Client interface could trigger an unintended background login request. [PO-1411]
• New payment gateway version available for Touchnet customers. For more information, see Payment Gateway Module Release history. [PO-4327], [PO-4404]
• Fixed an issue where upgrading to version 26 could cause the Application Server service to fail at startup if legacy custom memory configurations (such as MaxRAMFraction) were used in server.conf. Most environments are automatically migrated to modern arguments, but some edge cases may require manual intervention, this was due to a Java update. See known issue PO-4393 for more information.
• Fixed an issue on the Users page where sorting the user list by balance could cause the page to crash when the ‘multiple personal accounts’ feature is enabled. [PO-4415]
• Fixed an issue on the Printers page where disabling a printer could cause an error screen to display, locking the administrator out of the printer’s settings. [PO-4372]

Security

• PaperCut NG/MF Version 26 includes upgrades of core dependencies and several third-party libraries. [PO-3782], [PO-4156], [PO-3511], [PO-4227], [PO-3567], [PO-4224], [PO-4063], [PO-4109], [PO-4277]
• Significant improvements to internal user authentication speed. The hash encode strength was set too high. The default is now 12. Admins can change the strength in the security.properties file by editing user.internal.hash-encode.strength to a value between 4 and 31. [CDSS-6543]

Other notes

• This version contains a database upgrade.