Sign Live! cloud suite gears

Sign as you want!

In the age of digitization there are more and more electronic documents that are used in various business processes and require different signatures. A simple signature with a “manual” signature may be sufficient for one business process, an electronic seal is also required for another. Still other business processes require the written form and thus a qualified electronic signature that is created via a local smart card or remote signature.

FAQs for Sign Live! cloud suite gears

"Liquibase" - error when starting the WebApp core

This error occurs e.g. For example, if you have deactivated the "demo" profile.
In this case, the following entry is required in gears.properties:

spring.liquibase.enabled = false

created: 15.08.2019/XNUMX/XNUMX
Updated: 15.08.2019

MS EDGE: Prevent security question when calling SLcs bridge

The message can be switched off for a specific protocol using a RegistryKey:

[HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Internet Explorer \ ProtocolExecute \ csbridge]
"WarnOnOpen" = dword: 00000000

or

[HKEY_CURRENT_USER \ SOFTWARE \ Microsoft \ Internet Explorer \ ProtocolExecute \ csbridge]
"WarnOnOpen" = dword: 00000000

For more information, see https://stackoverflow.com/questions/37702082/internet-explorer-or-edge-how-to-display-the-warning-that-appear-if-you-open-c?rq=1

 

Process files> 2 MB (maxPostSize)

You can do this in Increase or cancel \ conf \ server.xml via the maxPostSize parameter (-1):

    <Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout = "20000"
               maxPostSize = "- 1"
               redirectPort = "8443" />

 

https://tomcat.apache.org/tomcat-9.0-doc/config/http.html

 

BSI security warning about log4jShell

intarsys products are not affected by the security problem!

You can find the following intarsys products in the supported versions continue to operate without changes:

  • PDF / A Live!
  • PDF / A Live! ZUGFeRD Toolkit
  • Sign Live! CC
  • Sign Live! CC DATEV edition
  • Sign Live! CC SPARKASSEN edition
  • Sign Live! cloud suite bridge
  • Sign Live! cloud suite gears
  • Sign Live! cloud suite SDK

The Java library that is causing the problem is in these products not .

This also applies to the Archisoft product from FHI-SIT in versions 1.1.1.8 and 1.1.1.9, which is sold by intarsys.

Product-specific explanations

  • In Sign Live! cloud suite gears Third-party products used up to version 8.7 are based on the critical Log4j version 2.14, but in the context of gears the dangerous library log4j-core- *. jar neither delivered nor used. There is therefore no potential risk.
  • With Sign Live! CC delivered Exampleimplementations (SDK / JMS) use Log4j version 1.x. These are only activated by calling the command line on the system and are also required a special Log4j configuration. They are therefore not considered to be a potential hazard.

Further safety information on the required basic components

tom cat 9 does not use Log4j in its basic configuration without standard and other web apps.

General safety information on the required basic components

Use the JVM in the required version (Java 11, SLcs gears: Java 8) at the most current patch level possible.
The Sign Live! CC / PDF / A Live! integrated JVM fulfills this (Java 11).
For Sign Live! cloud suite gears should be at least Azul JDK 8u312 + .

 

Further background information

 

 

We are here for you - contact us!

If you need information about our products:

 

  To contact form

 

  Sales  intarsys.de

Request whitepaper

white paper, Sign documents easily with Sign Live! download:

 

 To the whitepaper