Single signature

  •  PIN Input per document
  •  Ideal for processing individual documents including simple workflow support with CoSiMA

 

 Learn more

Batch signature

  •  PIN Input for multiple documents
  •  Sign your documents like you would in a signature folder

 

 Learn more

Comfort signature

  •  Unique PIN input
  •  Ideal for processing individual documents in the workflow

 

 Learn more

Sign Live! CC signature client

Signature directly on PC-Workplace

Sign Live! CC signature client is an advanced PDF-Viewer and signature application component at the same time (SAK) at the PC- Workstation for individual, batch and convenience signature with smart card, eToken, HSM, "Signing Service", etc. as well as for the time stamp signature. Sign Live! CC supports working with PDF-Forms and data can be recorded and saved directly.

Configurable services for file monitoring, virtual PDF-Printer connection and direct call options via web service interfaces (HTTP/SOAP) offer integration into almost any specialist application, ERP- and financial software of your IT-Surroundings.

Leading trust service providers in Germany, but also in Switzerland, recommend Sign Live! CC signature client as a signature product.

 

Single signature

Sign Live! CC signature client single offers the possibility in one PDF-Document to generate a signature field with a mouse click and to place an electronic signature and certificate information as well as other additional information there. In addition to the standard information from the certificate, individual, process-relevant information can also be defined. In addition, the integrated signature assistant offers the option of adding an image or logo that gives the signature an individual appearance.

This means that typical documents in workflow processes can be electronically signed by employees in a legally secure manner, even across several hierarchy or approval levels. Printouts and mailing become superfluous, possible sources of error are further reduced. Instead, your processing times are significantly shortened and your processes achieve greater efficiency and quality.

 

Signature workflow with CoSiMA

CoSiMA consists of dialog-oriented and preconfigured function blocks and includes system components for converting the input data stream and recognizing and processing key words in the input data. CoSiMA's user interface and dialogs are optimally designed for the user and can be easily adapted in dialog for the respective application, even without programming knowledge.

Regardless of whether you want to create signatures for contracts, offers or other important documents in companies that have to meet legal requirements or internal quality and compliance guidelines, you simply print your document and CoSiMA ensures that

  • the document in PDF is converted
  • if desired, important key information such as B. customer number, recipient, invoice number can be determined fully automatically from the document
  • the PDF-Document is qualified or advanced signed
  • the signed document is attached to an e-mail template and sent by e-mail
  • Finally, if you wish, a filing together with index data in one DMS or archive system.

Sign Live takes all of these process steps away from you! CC CoSiMA with a click of the mouse. Signing and sending electronic documents has never been easier.

  Product data sheet   data sheet   Video of CoSiMA   Buy in the shop

Batch signature

Sign Live! CC signature client batch is especially for users who want to sign several documents in a single step to save time and money. After just one time PIN-Entries are electronically signed in a batch of up to 25, 100, 250 or 1.000 documents and files in various formats. During this signature process, different signature formats can also be used for a specific document. The batch processing definitions required for this are already preconfigured and can be easily adapted in the dialog.

Extension for replacing scanning to BSI TR-RESISCAN

The Option TR-RESISCAN for Sign Live! CC signature client batch there are additional functions for the process of the replacement scan after the BSI TR-RESISCAN to disposal:

  • Embedding the batch signature in a configurable process kit.
  • Configurable visual inspection (spot check) according to protection requirements analysis TR-RESISCAN.
  • Addition of transfer notes and integration into the PDF-Scan product before integration backup. If the scan is in PDF/A2 delivered is the resulting document PDF/A3-compliant.

  Product data sheet    data sheet   Option TR-RESISCAN

 

Comfort signature

Convenience signature means the continuous signing of several documents which are passed one after the other to the signature application component. All in Sign Live! available interfaces can be used for this.

Sign Live! CC signature client comfort offers the possibility of combining convenience signature and workflow automation without major implementation effort for:

  • Approval processes, such as the four-eyes principle for orders, contracts, ...
  • electronic discharge and doctor's letters with dispatch via KV-CONNECT
  • and much more.

  Product data sheet   data sheet   Video of CoSiMA

FAQs for Sign Live! CC signature client

TRUST LISTS (TSL): - Update failed

With Brexit that has UK closed his trusted list. As a result, updating trusted lists may fail.

For Sign Live! CC Versions older than version 7.1 6 do not have a hotfix. In this case, you have to migrate to the current version.

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!
  • 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

 

 

BNotK Card: Can this be used in Sign Live! CC be used?

In future, the Federal Chamber of Notaries will provide its signature certificates via the remote signature service and no longer via a personal signature card.
The authentication for signature creation at the remote signature service is carried out using a personal smart card.

This requires a completely new procedure for signature creation. This signature is not triggered via the signature device "signIT smartcard CC", but via "signIT BNotK". When signing in the signature assistant, please select the appropriate signature device. If the dialog for selecting the signature device is not displayed in the signature assistant, it has been hidden. Via "Show all pages" in "Extras > Settings > Signatures > Signature creation > Signature assistant" you ensure that all dialogs appear again the next time the signature assistant is called up.

  • If your signature certificate is not available in the "Choose Identity" dialog, please contact the Support of the Federal Chamber of Notaries and ask whether the qualified signature certificate is available.
  • 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! CC from a specialist application, please inquire with the manufacturer whether the new signature device has been connected.  

What is an LTV (Long Term Validation) signature?

Whether a signature is valid, i.e. valid, should be verifiable 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 one CA (Certificate Authority) of this certificate at the time of creation of the end user certificate trustworthy and the root certificate valid?
  • What level of quality was the certificate used? Simple, advanced or qualified?

In order to be able to reliably answer these questions, a validation application such as Sign Live! several exams. An important aspect of this check is blocking checks using OCSP (Online Certificate Status Protocol) i.e. queries from the trust service provider (VDA) who issued the end-user certificate used. So that these OCSPQueries can be made, this service must be dated VDA online (directory service). The answers of the VDA are in turn signed by the latter so that the trustworthiness can be checked and thus ensured. This in turn takes place with the inclusion of OCSP-Interrogate. How this is to be done in full is determined by international standards (ETSI) regulated. 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? There may be a temporary malfunction if the required directory service is simply not available online. Or what if this is done by setting the VDA was switched off? The central deletion of information after the retention period has expired is also an incision. The end user certificate used cannot be checked in such cases and thus the complete signature verification does not lead to a clear result.

Different with LTV-Signatures. With this type of signature, all the required information is provided, again in accordance with international standards (ETSI), embedded in the signature. In case of PDFDocuments and signatures, for example, through the PAdES standard (ETSI EN 319 142) in the context of PAdES-B-LT-Profiles technically regulated.

The necessary information can be embedded both during the signature creation and later during validation. However, it is seldom that this takes place when the signature is created, since the time required for the signature creation is also followed by the verification. This is how enrichment is offered to LTV-Signature during validation before archiving. 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.

Perform the LTV-Signature even more?

How the validity of certificates is checked depends on different models (chain, shell or modified shell model). These different models also make perfect sense for the different uses of certificates. The validity of a SSL-Certificates should be checked differently in the browser than a certificate that was used to sign documents that must 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 period of validity.

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

How does a LTV-Signature with Sign Live! CC generated?

  You can find the answer in our tutorial


Status: February 2020

SIGNING: What do you need to create a qualified signature?
Mac OS X - Sign Live! CC.app cannot be opened

Takes place after the update of MAC OS X after installing Sign Live! CC the error message “Sign Live CC.app cannot be opened because Apple cannot search for malware in it. ”, Sign Live! CC opened as follows:

Right click, select Open, confirm dialog.

 

Updated: 10/2020
Recorded: 11/2019

 

 

SIGNING: Signing in the ZSVR - Packaging Register - (LUCID)

General

Whoever brings packaged goods into circulation is subject EU-wide the so-called extended product responsibility. This means that he has to take responsibility for ensuring that this packaging has the least possible impact on the environment. This costs money and was previously regulated in the Packaging Ordinance (VerpackV). On January 01st, 2019, the VerpackV was replaced by the   Packaging Act replaced. To implement the packaging law, the Central Office for Packaging Register Foundation (ZSVR) brought to life.

The ZSVR aims to ensure a transparent and fair distribution of the costs of the disposal and recycling system for the yellow bins / yellow bags (   "Dual System") to establish itself in the market. Every commercial first-time distributor of filled sales packaging, which is typically incurred by the end consumer or at the so-called equivalent waste disposal sites, has to be in the packaging register of the ZSVR be registered with their master data and the brands they sell. (Source: Wikipedia).

Anyone who puts “packaging subject to system participation” into circulation in Germany must contact the ZSVR im Packaging register LUCID to register. One of the technical requirements is the availability of suitable signature software such as Sign Live! CC listed. Further information can be found on the website of the ZSVR   here .

Signature with Sign Live! CC

LUCID

For the packaging register must embedded Signatures in PAdES format be generated. PDF-Signatures are in Sign Live! CC standard in the required format PAdES created.

How to create an embedded signature in Sign Live! CC:

  • Starten Sie Sign Live! CC
  • Open the PDFFile with File> Open menu item
  • The signature process is carried out via the menu Tools> Signature Functions> Sign Document started.
  • Select PDF Signature - PDF-internal signature after PDF-Specification and press [Next].
  • In the window Signature field position select the option Create a new signature field. After pressing [Next] the mouse pointer changes. Now drag on the with the left mouse button pressed PDF a field in the desired position in the desired size.
  • As soon as you release the left mouse button, the window opens Signature field representation. Choose here Standard [Continue].
  • Select as signature device You SignIT smartcard CC - Sign with a signature card and card reader at the workplace [Continue]. If you have not already done so, please insert the signature card into the card reader.
  • Im Identity window the card reader used and the certificate from the signature card are displayed. Depending on the setting, several certificates can be displayed. Please select the certificate with the Purpose: qualified signature [Continue].
  • The Attribute Certificates window can with [Next] skipped .
  • You will now be able to enter your personal PIN asked. Enter the PIN on the card reader and confirm your entry also on the card reader.
  • The successful signature is saved in Sign Live! CC displayed in the left application window.

Please note that in order to create a qualified signature Sign Live! CC must be licensed. A license for Windows or Mac OS can about our  Shop can be acquired.

Created: 23.05.2019/XNUMX/XNUMX
Updated: 23.05.2019/XNUMX/XNUMX

We are here for you - contact us!

If you need information about our products:

 

  To contact form

 

  Sales  intarsys.de

application scenarios

  Contracts and documents that require the written form

  eDoctor's letter, findings, blank forms (e.g. sample 10) and patient information sheets

  Signature creation in conjunction with eANV systems (NachwV)

  Temporary employees (§12 AÜG)

  Electronic communication in the judiciary (JKOmG, ZPO)

  e-procurement