Welcome to intarsys
Signature creation

Sign Live! CC client batch

Sign Live! CC client batch

The workplace-based solution for creating signatures in batches

sign

Create and verify digital signatures in batch

with Sign Live! CC signature client batch

Creation of signature, seal and time stamp

  • LTV signatures for long-term archiving raise
    • Embedded chain of trust, timestamp and revocation information (OCSP, CRL)
    • Extending the lifetime of existing signatures
    • Embed signature validation information (DSS)
  • Approval and certification signature in the PDF or PDF/A document
  • Apply individual, freely selectable signature image representation (page, size, color, position, text, logo, background image, etc.)
  • Read information from the certificate and attach it visibly

Validation of signature, seal and timestamp

  • Qualified and/or advanced electronic signature, seal and time stamp in accordance with EU regulation eIDAS, Trust Services Act (DE) and CertES (CH) check
  • Signature status display with detailed validation result
  • Create extensive test report in PDF, XML and HTML format according to OASIS DSS
  • Extract the signed version (revision) of the document
  • Operating system independent certificate and revocation list management

Services and Miscellaneous

  • Printing service for creating a PDF document
  • Add, delete and open attachments of various file formats
  • Supports working with PDF forms
  • PIN management for signature cards (initialization, change, reset)

Create and verify digital signatures in batch

with Sign Live! CC signature client batch

Creation of signature, seal and time stamp

  • LTV signatures for long-term archiving raise
    • Embedded chain of trust, timestamp and revocation information (OCSP, CRL)
    • Extending the lifetime of existing signatures
    • Embed signature validation information (DSS)
  • Approval and certification signature in the PDF or PDF/A document
  • Apply individual, freely selectable signature image display (side, size, color, position, text, logo, background image, etc.)
  • Read information from the certificate and attach it visibly

Validation of signature, seal and timestamp

  • Qualified and/or advanced electronic signature, seal and time stamp in accordance with EU regulation eIDAS, Trust Services Act (DE) and CertES (CH) check
  • Signature status display with detailed validation result
  • Create extensive test report in PDF, XML and HTML format according to OASIS DSS
  • Extract the signed version (revision) of the document
  • Operating system independent certificate and revocation list management

Services and Miscellaneous

  • Printing service for creating a PDF document
  • Add, delete and open attachments of various file formats
  • Supports working with PDF forms
  • PIN management for signature cards (initialization, change, reset)

Do you prefer individual processing or comfort processing?

Product as single processing

Each signature creation requires a PIN entry

Then the following product is the right solution:

Go to Sign Live! CC client

Product as comfort processing

for up to 25 or 40 signatures with one PIN entry

Then the following product is the right solution:

Go to Sign Live! CC client comfort

It works that easy:

Extension for replacing scanning according to BSI TR-RESISCAN

The TR-RESISCAN option for Sign Live! CC signature client batch, further functions are available for the process of the replacing scan according to the BSI TR-RESISCAN:

Sign Live! CC the right solution for every industry

Accountants and tax advisers

administration and judiciary

HR management and employment contracts

Sign Live! CC client batch

The workplace-based solution for creating signatures for multiple documents with one PIN entry

Learn more about Sign Live! client batch

FAQs about the Sign Live! CC signature client

The new BNotK Card will be in Sign Live! C.C.C supported from version 7.1.11

In the future, the Federal Chamber of Notaries will issue its signature certificates via the remote signature service and no longer via a personal one Signature card provide.
Authentication for signature creation at the remote signature service is carried out using personal means Smart Card.

This requires a completely new approach to signature creation. This signature is not sent via the signature device “signIT smartcard CC” but rather via “signIT BNotK“. When signing, please select the appropriate signature device in the signature assistant. If your signature certificate is not available, please contact the support of the Federal Chamber of Notaries.

If you are using a Reiner SCT card reader with an RFID function, you must switch off the RFID function so that there are no problems reading the authentication certificate on your card.

If you Sign Live! C.C.C from a specialist application, please inquire with the manufacturer whether the new signature device has been connected.  

The presentation of the signature can be designed individually. The procedure is in the tutorial "Design signature field display" described which you here available for download. 
It is important to ensure that the last variable in the Appearance window contains a value. A newline as the last variable would lead to an error message (internal cryptographic library error).

For the qualified electronic signature you need in addition to the Software additionally a Signature card , and a Card reader.
You can obtain signature cards from trust service providers (VDA). The of Sign Live! C.C.C Supported signature cards and card readers can be found in our service description and system requirements.

Purchase the signature application software here Sign Live! C.C.C for different operating systems.

It should be possible to check whether a signature is valid, i.e. valid, even after many years. In order to be able to check a signature again, several pieces of information must be available:

  • Was the end user certificate used valid at the time it was used?
  • Was the issuing CA (Certificate Authority) of this certificate trustworthy at the time the end user certificate was created and was the root certificate valid?
  • What was the quality level of the certificate used? Basic, advanced or qualified?

To confidently answer these questions, a validation application such as Sign Live! several exams. An important aspect of this check are revocation checks using OCSP (Online Certificate Status Protocol), ie queries to the trust service provider (VDA) that issued the end user certificate used. In order for these OCSP queries to be carried out, this service must be made available online by the VDA (directory service). The replies from the VDA are in turn signed by the latter so that the trustworthiness can be checked and thus ensured. This is then done in turn with the inclusion of OCSP queries. International standards (ETSI) regulate how this is to be done in full. At the end of these queries, the validation application can then provide a trustworthy status of the end user certificate used.

But what if the necessary directory service is temporarily or permanently unavailable? A temporary disruption can occur if the required directory service is simply not available online. Or what if this was switched off by the VDA being discontinued? The central deletion of information after the retention periods have expired also represents a cut. The end user certificate used cannot be checked in such cases and therefore the complete signature check does not lead to a clear result.

LTV signatures are different. With this type of signature, all required information is embedded in the signature, again according to international standards (ETSI). In the case of PDF documents and signatures, this is technically regulated, for example, by the PAdES standard (ETSI EN 319 142) in the context of the PAdES-B-LT profile.

The necessary information can be embedded both when the signature is created and later during validation. However, it is rare for this to happen when the signature is created, since the time required to create the signature also includes the time required for verification. The enrichment of the LTV signature for validation before archiving is therefore a good idea. From this point on, the signature is always checked offline and takes place without access to the directory service. A check is therefore independent of the availability of this service, regardless of the reason why it is not available.

Does the LTV signature do even more?

How the validity of certificates is checked is based on different models (chain, shell or modified shell model). These different models also make sense for the different uses of certificates. The validity of an SSL certificate should be checked differently in the browser than a certificate that was used to sign documents that have to be verifiable for decades.

Let's take Adobe Reader as an example. Adobe Reader will no longer classify a signature as trustworthy after the end user certificate used has expired, even if the signature was made during the validity period.

This behavior can be avoided by the LTV signature if the LTV signature is done before the expiration date. With the timely LTV signature, the Adobe Reader tick stays green and the signature continues to be positively checked - permanently. This is an important step on the way to greater user acceptance of the signature. 

How to create an LTV signature with Sign Live! CC generated?

Are intarsys products affected by the security vulnerability?

The BSI has the following security warning published.
The actual problem is explained in a PDF, which is continuously updated on the BSI website.
 

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:

  • Sign Live! C.C.C
  • 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! C.C.C 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

If you want to sign from GVS a BNotK-Map for remote signature, it is necessary to set this accordingly in GVS.
You can see an example of the settings here.

Also, please make sure that Sign Live! C.C.C is entered as the software to be used.

If you use software from Baqué & Lauter GmbH as a bailiff and with Sign Live! C.C.C want to sign must in Sign Live! C.C.C a certain "Service" to be set up.

If during the installation of the bailiff software the software Sign Live! C.C.C was already installed, this service should have been set up automatically. Otherwise, this can also be done manually. You will find the corresponding instructions here.

When opening very large files, the Sign Live! C.C.C The available memory is not sufficient (error message: ... "Java heap space"). The log provides information about the maximum memory Java requests from the operating system. Eg:


[2019.11.20-09:29:57.818][I][d.i.tools.logging][executor singleton][] maxmemory=477626368

First, check that the operating system can actually provide that much memory for Java. Operating system and other applications also require memory!
If enough memory is available, please gradually increase the memory claimed by Java.

So put in Sign Live! C.C.C more memory available:

  • Copy the fileINSTALLATION DIRECTORY> \ demo \ vmoptions \ more memory \* .vmoptions1 after \bin.
  • Starten Sie Sign Live! C.C.C New.
  • If the main memory is not sufficient, the value in the vmoptions file can be edited with an editor and the value can be increased to -Xmx2048m, for example. The maximum value depends on how much RAM is available on your computer.

Important note:

  • For operation as a Windows service, the signivecc_service.exe file must also be created with identical content.

1) The name of the vmoptions file depends on the operating system used.

Sign Live! CC starts with the language settings of the operating system.

To get the operating language of Sign Live! CC you need administrator rights to manipulate them.
Follow these steps:

  1. Quit Sign Live! CC.
  2. Use Windows Explorer to switch to the installation directory for Sign Live! CC. In most cases this is "C:\Program Files\Sign Live CC " or "C:\Program Files (x86)\Sign Live CC".
  3. Navigate further into the subdirectory "demo\vmoptions\language english".
  4. Copy the SignLiveCC.exe.vmoptions file from this directory.
  5. Change to the “bin” subdirectory of the installation directory Sign Live! CC and drop the SignLiveCC.exe.vmoptions file there.
  6. Starten Sie Sign Live! CC new so that the language settings are loaded.

By doing this, the entire user interface of Sign Live! CC presented in English.

To reset to German, delete the "SignLiveCC.exe.vmoptions" file from the bin directory and start it Sign Live! C.C.C New.

Stay up to date with our newsletter!

And get all the information about:

Products

Services

Events

Activities

The first customers use digital process structure for holistic workflows Hollern, Karlsruhe and Taucha, November 07.11.2023th, XNUMX - The companies GekoS mbH from Hollern in Lower Saxony and procilon