Skip to main content

Change Logs
signoSign/Universal

Important notes
  • If STARTTLS is enabled, which is the default setting, emails are no longer sent unencrypted when the mail server does not support STARTTLS. Instead, sending fails with an error. If your mail server does not support encrypted connections, set smtp.startTlsEnable=false in the settings.properties file.
New features
  • You can now send emails through mail servers that use implicit TLS, usually on port 465. To do so, set the new setting smtp.useTls=true in the settings.properties file. signoSign/Universal then tries implicit TLS first and STARTTLS second. If neither connection can be established, sending fails with an error.
Changes
  • Updated third-party components to fix known security vulnerabilities.
  • The help menu in workflow folders is now hidden.
Bug fixes
  • Fixed an issue where the viewer and the Document Pool loaded fonts from Google servers, which transmitted users’ IP addresses to Google. The fonts are now provided by signoSign/Universal itself.
  • Fixed an issue where single logout (SLO) did not work with OpenID Connect identity providers such as Microsoft Entra ID (formerly Azure AD), so users were signed in again immediately after logging out.
  • Fixed an issue where signing failed with an error if the configured time stamp server required a user name and password.
  • Fixed an issue where opening the viewer could redirect users to an internal server address instead of the public URL configured in web.ssmPublicUrl, so the document could not be signed. This could occur behind a reverse proxy or gateway when the viewer session was no longer available, for example after it had expired.
  • Fixed an issue where the Document Pool reported an email as sent successfully even though sending had failed.
  • Fixed an issue where long messages in workflow folders were sometimes wrapped in the middle of a word.