Open accessibility options
Depending on the characteristics of the license you are using, various actions may have restrictions. An example is the number of possible signatures per day.
If several Windows services from Sign Live! CC are operated in parallel, a name must be specified when installing the service. To do this, adjust the file
Variables are passed when starting Sign Live! CC using the file “bin\SignLiveCC.exe.vmoptions”. These are defined using the option “-Dproperty = value” and a value is set.
When reinstalling Sign Live! CC or when changing computers, adopting settings from an existing installation can be helpful. The Sign Live!
When validating, the validity of certificates is usually first checked via OCSP query (online status query). This requires access to the Internet. First
In cases where the validating Sign Live! CC instance does not have/may not have an internet connection and therefore cannot reach the TL server, the following is possible
To validate signatures, Sign Live! CC always have current root certificates, which are distributed via trust lists (Trusted List-TL), at least for the eIDAS-PKI. Sign Live! C.C.C
When trust centers switch to a new PKI infrastructure, it may happen that signatures or timestamps created with very new signature cards/certificates are not validly validated
The default configuration for the SLCC application log is stored under \classes\config\logback.xml The appender “FILE” is responsible for the SLCC application log. Adjustments must therefore be made there. To change the location/number/size of the
On rare occasions, Sign Live! CC or Sign Live! cloud suite bridge after installation does not start and that the following
Publicly appointed surveyors can use electronic signatures according to eIDAS regulation use (Leipzig, 26.02.2025) Since the beginning ...
