XIMA and procilon GROUP enter into a partnership Taucha, Dresden April 04.04.2023th, XNUMX – FORMCYCLE is a low-code application from the Dresden-based XIMA MEDIA GmbH, the administrations at
Software Download Sign Live! CC
Title | Version | Release Date | Download |
---|---|---|---|
Sign Live! CC Mac OS X 64-bit 179.81 MB |
7.1.11.2 | 17 January 2023 | Download |
Sign Live! CC Windows 32-bit 164.63 MB |
7.1.11.2 | 17 January 2023 | Download |
Sign Live! CC Windows 64-bit 163.74 MB |
7.1.11.2 | 17 January 2023 | Download |
You don't have a license for Sign Live! CC?
Then you can easily purchase them in our shop:
Before installing, please read the release notes:
Release Notes
Sign Live! C.C.C
Sign Live! C.C.C
Current version
In the previous versions of Sign Live! C.C.C When using a BNotK card (for remote signature), the maximum number of characters when entering the PIN was limited to 8 characters. As of version 7.1.11.2, you can enter up to 16 characters. Further changes compared to the previous versions can be found in the release notes
A migration guide for Sign Live! C.C.C see here .
If you need support with migration and/or installation, please email us for a quote sales@intarsys.de .
To operate the version 7.1.11.2 please install the latest component.
Installation:
Should you use Sign Live! If you have installed CC version 7.1.x, version 7.1.11.2 can be installed in the same directory. The licenses are automatically transferred.
When updating from version 7.0.x to version 7.1.11.2, the Installation in a new directory take place. The licenses must then be imported again. If you need support for installation or migration, please get an offer by email sales@intarsys.de .
If you use Sign Live! CC within or in combination with another partner software use, talk about installing the new version please beforehand with the manufacturer of this application. Should the manufacturer update the current version 7.1.11.x of Sign Live! If you do not support CC yet, you may no longer be able to use the partner's application.
Notice to users who Sign Live! C.C.C as a client for Sign Live! cloud suite gears use:
This release introduces support for LT level signatures created by Gears and PAdES specific semantics.
This requires correct handling of the requested signature format on both sides, the Sign Live! CC Client and Gears.
To use the default mechanisms and settings, please make sure you update your gears server to V8.8.1 or newer.
Other versions
The change compared to the previous versions can be found in the release notes
A migration guide for Sign Live! C.C.C see here .
If you need support with migration and/or installation, please email us for a quote sales@intarsys.de .
If you still need version 7.1.11.1, please contact our support, which you can find at support@intarsys.de .
Installation:
Should you use Sign Live! If you have installed CC version 7.1.x, version 7.1.11.1 can be installed in the same directory. The licenses are automatically transferred.
When updating from version 7.0.x to version 7.1.11.1, the Installation in a new directory take place. The licenses must then be imported again. If you need support for installation or migration, please get an offer by email sales@intarsys.de .
If you use Sign Live! CC within or in combination with another partner software use, talk about installing the new version please beforehand with the manufacturer of this application. Should the manufacturer update the current version 7.1.11.x of Sign Live! If you do not support CC yet, you may no longer be able to use the partner's application.
Notice to users who Sign Live! C.C.C as a client for Sign Live! cloud suite gears use:
This release introduces support for LT level signatures created by Gears and PAdES specific semantics.
This requires correct handling of the requested signature format on both sides, the Sign Live! CC Client and Gears.
To use the default mechanisms and settings, please make sure you update your gears server to V8.8.1 or newer.
The changes compared to the previous versions can be found in the release notes
A migration guide for Sign Live! C.C.C see here .
If you need support with migration and/or installation, please email us for a quote sales@intarsys.de .
If you still need version 7.1.10, please contact our support, which you can find at support@intarsys.de .
Installation:
Should you use Sign Live! If you have installed CC version 7.1.x, version 7.1.10 can be installed in the same directory. The licenses are automatically transferred.
When updating from version 7.0.x to version 7.1.10, the Installation in a new directory take place. The licenses must then be imported again. If you need support for installation or migration, please get an offer by email sales@intarsys.de .
If you use Sign Live! CC within or in combination with another partner software use, talk about installing the new version please beforehand with the manufacturer of this application. Should the manufacturer update the current version 7.1.10 of Sign Live! If you don't support CC yet, you could otherwise no longer be able to use the partner's application.
Notice to users using Sign Live! CC as a client for Sign Live! use cloud suite gears:
This release introduces support for LT level signatures created by Gears and PAdES specific semantics.
This requires correct handling of the requested signature format on both sides, the Sign Live! CC Client and Gears.
To use the default mechanisms and settings, please make sure you update your gears server to v8.8.1 or newer.
Discontinued on: 30.11.2022/XNUMX/XNUMX
Patch version for Sign Live! CC 7.1.9.
Installation:
Should you use Sign Live! If you have installed CC version 7.1.x, version 7.1.9.1 can be installed in the same directory. The licenses are automatically transferred.
When updating from version 7.0.x to version 7.1.9.1, the Installation in a new directory take place. The licenses must then be imported again. If you need support for installation or migration, please get an offer by email sales@intarsys.de .
If you use Sign Live! CC within or in combination with another partner software use, talk about installing the new version please beforehand with the manufacturer of this application. Should the manufacturer update the current version 7.1.9.1 of Sign Live! If you don't support CC yet, you could otherwise no longer be able to use the partner's application.
Notice to users using Sign Live! CC as a client for Sign Live! use cloud suite gears:
This release introduces support for LT level signatures created by Gears and PAdES specific semantics.
This requires correct handling of the requested signature format on both sides, the Sign Live! CC Client and Gears.
To use the default mechanisms and settings, please make sure you update your gears server to v8.8.1 or newer.
Note for macOS users:
The restriction for Monterey has been removed with this version.
Discontinued on: 30.11.2022/XNUMX/XNUMX
If you still need version 7.1.9, please contact our support, which you can find at support@intarsys.de .
Notice to users who Sign Live! C.C.C as a client for Sign Live! cloud suite gears use:
This release introduces support for LT level signatures created by Gears and PAdES specific semantics.
This requires correct handling of the requested signature format on both sides, the Sign Live! CC Client and Gears.
To use the default mechanisms and settings, please make sure you update your gears server to v8.8.1 or newer.
Note for macOS users:
The restriction for Monterey has been removed with this version.
Discontinued on: 30.11.2022/XNUMX/XNUMX
Patch version for Sign Live! CC 7.1.8.
NOTE for MAC users: If you are using a macOS Big Sur or older system, please install Sign Live! CC 7.1.8.
If you still need version 7.1.8, please contact our support, which you can find at support@intarsys.de .
Installation:
Should you Sign Live! C.C.C version 7.1.x installed, version 7.1.8.1 can be installed in the same directory. The licenses are automatically adopted.
In case you Sign Live! C.C.C within or in combination with another partner software use, talk about installing the new version please beforehand with the manufacturer of this application. If the manufacturer has the current version 7.1.8.1 of Sign Live! C.C.C not yet support, otherwise you may no longer be able to use the partner's application.
Discontinued on: 30.11.2022/XNUMX/XNUMX
NOTE for MAC users:
This version is not released for macOS Monterey
Installation:
Should you Sign Live! C.C.C version 7.1.x installed, version 7.1.8 can be installed in the same directory. The licenses are automatically adopted.
When updating from version 7.0.x to version 7.1.8, the Installation in a new directory take place. The licenses must then be imported again. If you need support for installation or migration, please get an offer by email sales@intarsys.de .
In case you Sign Live! C.C.C within or in combination with another partner software use, talk about installing the new version please beforehand with the manufacturer of this application. If the manufacturer has the current version 7.1.8 of Sign Live! C.C.C not yet support, otherwise you may no longer be able to use the partner's application.
Discontinued on: 30.11.2022/XNUMX/XNUMX
- From this version, the signature card D-TRUST eHBA Generation 2.0 unterstützt.
- Customers who Sign Live! C.C.C for validation processes via SignLiveAPI, please update the software.
- Customers who create XML signatures and send them to ZKS-Abfall, please update to the current version.
- The hotfix for the update of the "Trusted List" is included.
Discontinued on: 30.11.2022/XNUMX/XNUMX
- From this version onwards, the use of the D-TRUST 4.1 smart card and the D-TRUST 4.4. smart card is possible.
- If you are using this version, please note that you must import Sign Live CC 7.1.6 – Hotfix Trusted List Update to update the trust lists.
The trust lists cannot be updated without this hotfix, since the UK has its trusted list has closed. In Sign Live! CC version 7.1.7 Updating the trust lists runs smoothly. - There may be display problems when scrolling under MAC OS. By importing Sign Live! CC 7.1.6 – Hotfix fixed macOS rendering.
In Sign Live! CC version 7.1.7 this display problem no longer exists.
Discontinued on: 30.06.2021/XNUMX/XNUMX
This version includes the one made available for version 7.1.5 Hotfix PDF Shadow Attack.
Discontinued on: 30.06.2021/XNUMX/XNUMX
With this release, multiple XAdES signatures can be created with the XML signature creation wizard.
Discontinued on: 31.03.2021/XNUMX/XNUMX
This version includes an update of the "Trusted Lists"
Use our Sign Live FAQs and tutorials! CC:
FAQ's
Tutorials
FAQ's
General (install, license...)
In rare cases it happens that Sign Live! C.C.C or Sign Live! cloud suite bridge not start after the installation and that the following error message appears with possible error causes:
Practice has shown that the causes of error listed in the error message often do not lead to a solution to the problem. Another possible cause is that a required Microsoft Visual C++ runtime library is missing or outdated.
This runtime library is available in the Microsoft Visual C++ Redistributable package.
Please check the Windows settings under "Apps and Features" to see whether the current version of this software package is available on your computer.
Es wird at least the package with the Year number 2015-2019 or a newer version is required.
If this package is not available or is an older version, please update and then restart the intarsys application.
The current versions of the software package can be found at:
https://aka.ms/vs/17/release/vc_redist.x64.exe (for the 64 bit version of the application)
https://aka.ms/vs/17/release/vc_redist.x86.exe (for the 32 bit version of the application)
The standard configuration for the SLCC application log is stored under
\classes\config\logback.xml
The “FILE” appender is responsible for the SLCC application log.
So adjustments have to be made there.
To change the location/number/size of the log files to be created, change and/or .
You can find information on this under http://logback.qos.ch/manual/appenders.html.
To customize the layout of the log file, change this to suit your needs.
Information on the variables used in it can be found under
http://logback.qos.ch/manual/layouts.html
% p /% le /% level are e.g. B. for the level designation.
When reinstalling Sign Live! C.C.C or when changing computers, it can be helpful to adopt settings from an existing installation.
The settings of Sign Live! C.C.C are stored in the profile directory of the application.
- (Windows client: C:\Users\\.SignLiveCC_.)
- (Windows server: C:\ProgramData\.SignLiveCC_.)
The following subdirectories can be adopted:
"preferences" (includes settings made via "Extras > Settings")
"instruments" (includes configurations of service containers, signature pools, timestamps, configurations for signIT gears, etc.)
"licenses" (may include the license)
"db" (should be adopted if own certificates are stored in the certificate store of Sign Live! C.C.C were imported)
A quick guide to migration is available as a Tutorial ready for download.
Variables are used when Sign Live! C.C.C using the bin\SignLiveCC.exe.vmoptions file. These are defined using the "-Dproperty = value" option and a value is set. Environment variables can also be specified as values.
Examples:
-Dmy.test = test -Dmy.profile = $ {USERPROFILE}
These variables can be used, for example, when configuring Sign Live! C.C.C via ${properties.my.test} or ${properties.my.profile}.
For more information on using the vmoptions file, see the Users Guide from exe4jused to create the Sign Live! C.C.C Launchers for Windows is used.
Should several Windows services from Sign Live! C.C.C are operated in parallel, a name must be specified when installing the service. To do this, customize the bin/SignLiveCC_service_install.bat file by specifying a name after the /install option.
Example:
……./install MySLCCService
The same name must be specified in the bat files for starting, stopping and uninstalling the Windows service.
Parameters for use in Sign Live! C.C.C Windows services are passed using the "bin/SignLiveCC_service.exe.vmoptions" file. You can find more information on this here.
It may make sense to replace the with Sign Live! C.C.C to use your own JVM.
For example, if you access the via JMX Sign Live! C.C.C Want to access MBeans or the application remotely debug want.
Follow these steps:
- Name the directory with Sign Live! C.C.C delivered JVM.
Windows: C:\Programs\SignLiveCC_7.1\jre --> C:\Programs\SignLiveCC_7.1\jre_off Linux: /opt/intarsys/signlivecc-7.1.7/bin/jre --> /opt/intarsys/signlivecc-7.1.7/bin/jre_off - Windows:
Define the root directory of the JVM to be used via the Windows system settings in the system variable EXE4J_JAVA_HOME (without the trailing "\").
If this does not lead to success, also define EXE4J_LOG=yes to get information about the behavior of EXE4J:
During operation, a message box provides information about where the log is stored.
Linux:
Set $CABARET_JAVA_HOME to the root directory of the desired JVM
(see also information in /opt/intarsys\signlivecc-7.1.7/bin/signlivecc.sh)
3. Start Sign Live! C.C.C new. You should now find the defined JVM in the log under java.home.
Important NOTE
With Sign Live! C.C.C delivered JRE uses the keystore.type = jks.
Separately installed JRE/JDK must be adjusted accordingly.
To do this, set in your Java installation in the file java.security --> keystore.type = jks.
When creating an installation medium for Windows, the software "InnoSetup" from "JRSoftware" is used.
Innosetup supports the "Silent Install" function. Installation parameters recorded once can be used in subsequent installations.
Example:
Create a file with your installation parameters by calling the following command line:
- setup_SignLive_CC_JRE_6.2.1_64Bit.exe /SAVEINF="c:\temp\install.inf"
Adjust the file if necessary and use the saved parameters via the call
- setup_SignLive_CC_JRE_6.2.1_64Bit.exe /SILENT /LOADINF="c:\temp\install.inf"
for further installations.
You can find more call parameters for Innosetup here
Note: If you have already installed the application in a same version or a previous version or if you are installing a patch:
- Exit the application, preferably via the system tray (taskbar), if it is running.
- If you have configured the software as a Windows service, stop the Windows service.
How to install the software on a Microsoft Windows system:
- Download the installation file with the extension ".exe".
- Run the downloaded setup file (double click).
- Start the installed application if it does not start automatically.
- Licensing is required to be able to use the software to its full extent.
You will find step-by-step instructions for downloading the software, installation and licensing here.
How to install the software on a Linux system:
- Download the file with the extension ".tar.gz".
- If you have already installed the application in a previous version or if you are installing a patch:
- Quit the application if it has started.
- If you have configured the software as a Linux service, stop the Linux service.
- Unzip the downloaded file as follows, using the file name of the downloaded file plus the version number as the name for the installation directory:
tar -xf signlivecc_*.tar.gz -C /var/signlivecc-7.1.11/ - Check your installation.
- Start the installed application.
Note: You should also unzip an update into a new directory in order to avoid the contents of different versions in the installation. Specific adjustments must be carried out again or adopted after the installation.
Note: Depending on the product, the file name of the downloaded file is different. For the example in point 3, the product 'Sign Live! C.C.C, used.
To install the software on an Apple MacOS system:
- Download the file with the extension ".dmg".
- If you have already installed the same version or a previous version of the application: Quit the application, if it is started.
- After double-clicking on the DMG file (the disk image), a virtual drive appears in the finder.
- Drag the application icon into the application directory.
- Check your installation.
- Start the installed application.
To install a patch to an existing version:
- Download the file with the extension ".dmg".
- Please make sure that the application "Sign Live! C.C.C” was started and stopped before installing the patch or exit the application if it was started.
- After double-clicking on the disk image, the appears Sign Live! C.C.C patcher app.
- Run Sign Live! C.C.C Double-click Patcher App.
- Check the version number displayed and confirm that you want to apply the patch.
- Choose the appropriate installation directory from Sign Live! C.C.C and start the installation.
- After installing the patch, a success message appears.
- Check your installation.
- Start the installed application.
For step-by-step instructions on downloading the software, installation and product activation, visit our Tutorials.
A font copied into the fonts directory is not displayed in an intarsys product and cannot be used. What should I do?
Our products read the fonts from the standard directory. On Windows this is C: \ Windows \ Fonts. In the user view, not only the fonts from this directory are displayed, but also the fonts from the user directory. This can only be seen when the properties of a font are displayed.
Copied If you put a font in the directory C: \ Windows \ Fonts, it will be displayed there, but is de facto in the user directory. Our software does not access the user directory by default, so the font is not available even though you see it in the supposedly correct place.
Solution:
- Install the font instead of copying it. Use this for that context menu (right mouse button) and choose "Install for everyone". This will put the font in the correct directory.
Sign Live! C.C.C
The current information about the operating systems and the tested hardware (e.g. signature cards and card readers) can always be found in the current data sheet. Thin client scenarios based on Windows Terminal Server or Citrix Presentation Server are also supported.
The application runs smoothly. Problems arise only when processing large files. The decisive factor is the size of a file while processing in the application. This is due to the size in bytes and through their structure. Problematic are e.g. E.g. many pages (>100), large images.
The following typical error messages can be seen in the log:
- java.lang.OutOfMemoryError: Java heap space
--> You can find more information on this in the FAQ – Make more memory available - e.g. B. java.net.SocketException: Software caused connection abort: socket write error
--> see below
These problems can occur when using the SOAP protocol.
In this case, limiting settings must be increased.
To do this, create the file /classes/cxf/bus.properties e.g. B. with the following content:
org.apache.cxf.stax.maxTextLength = 512000000
and restart the application.
This increases the message size from approx. 100 MB (standard) to 512 MB.
Note that the message size is always larger than the actual file size (factor approx. 64) due to the base1,3 encoding.
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.
Setting up a PDF printer is required for various actions. This is done in Sign Live! C.C.C "Ghostscript" used.
When installing Sign Live! CC version 7.1.7 – or older – please use Ghostscript 9.53.3 or older.
Do you have Sign Live! C.C.C installed in the current version, the current version of Ghostscript can also be 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:
- Quit Sign Live! CC.
- 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".
- Navigate further into the subdirectory "demo\vmoptions\language english".
- Copy the SignLiveCC.exe.vmoptions file from this directory.
- Change to the “bin” subdirectory of the installation directory Sign Live! CC and drop the SignLiveCC.exe.vmoptions file there.
- 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.
When trust centers switch to a new PKI infrastructure, it can happen that signatures that were created with very new signature cards are not validly validated. This is due to the fact that the new Trusted Lists (TSL) and / or Root CAs were not yet implemented at the time our software was released.
The Update of the trust lists in Sign Live! C.C.C these signatures are validated again.
Via menu item Tools> Certificates> Update Trust Lists trigger the update of the trust lists manually.
When trust centers switch to a new PKI infrastructure, it can happen that signatures that were created with very new signature cards are not validly validated. This is due to the fact that the new Trusted Lists (TSL) and / or Root CAs were not yet implemented at the time our software was released.
The Update of the trust lists in Sign Live! C.C.C these signatures are validated again.
- Via menu item Tools> Certificates> Update Trust Lists trigger the update of the trust lists manually.
In server installations it makes sense to have the update triggered time-controlled. To do this, adapt the preconfigured service container:
- Via menu item Tools> Services> Service Container Management Configure the schedule of the "Trusted List Update Scheduler" service container and automatically trigger the update of the trust lists:
In cases where the validating Sign Live! C.C.C-Instance has / may not have an Internet connection and therefore cannot reach the TSL server, the following workaround is available:
- Install a Sign Live! C.C.CTSL instance on a computer that is permitted to access TSL servers on the Internet.
Version and patch level should match those of the Sign Live! C.C.CValidation instance. - Run on the Sign Live! C.C.C-TSL instance updating the TSL by using menu item Tools> Certificates> Update Trust Lists trigger the update of the trust lists manually.
The updated trust lists (TSL) can usually be found in the directory \tsl – for example C:\Users\\.SignLiveCC_7.\tsl - Replace on the Sign Live! C.C.C-Validation instance the contents of the directory \tsl by the TSLs on the Sign Live! C.C.C-TSL instance.
It is important that the replacement takes place completely! Everything else requires detailed know-how about the internal structure of the TSLs. - Run on the Sign Live! C.C.C -Reboot validation instance.
This workaround uses internal Sign Live! C.C.C- Processes that you cannot influence.
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. Once the limit is reached, the application continues to work very slowly.
- If the license used is not sufficient for you, please contact us at the e-mail address about a license upgrade support@intarsys.de in connection.
- It is best if you let us know the license key you are currently using. You can find this under the menu item EXTRAS > LICENSE MANAGEMENT at the far right.
- Information about current versions (updates) is provided via newsletters. With the appropriate setting, an update check is carried out on the software side. The update is not installed automatically.
- Please note:
- If you use our software in connection with third-party software, please inquire advance at the manufacturer whether the update is to be carried out.
- The license is usually inherited within a master release. A new license is required when changing the master release. In any case, please note the release notes.
- If you obtained the software from one of our partners, you will normally be informed accordingly by this partner.
- Since January 01.01.2019st, XNUMX, our licenses have generally been so-called term licenses with a defined expiry date. Until this expiration date the update to the current version is free of charge.
- Please check whether the manufacturer of your card reader provides drivers for MAC.
The company's card reader drivers PURE SCT are here available. - You can find a list of the signature cards and card readers that we have tested in the Sign Live! CC data sheet.
A hotfix too Sign Live! C.C.C is provided as a ZIP file. To install the hotfix, the zip file must be extracted and the file(s) it contains copied to a specific directory. This FAQ explains how to get the files into the application directory of Sign Live! C.C.C be copied.
Please note the information in the hotfix about the directory to which the files should be copied.
- If open, exit Sign Live! C.C.C
- For example, save the zip file to the desktop
- Double click on the zip file. This is automatically unpacked and the unpacked folders and files are made available
- Navigate to using the Finder Program, Mark your choiche Sign Live! C.C.C, Open the context menu and choose Show package contents. The "Contents" folder is displayed
- Open the folders Contents/Resources
- Copy the unzipped folders and files - which were made available in the previous step - into this folder or into the folder specified in the hotfix
- Launch Sign Live! CC new
SignLive! CC creates log files. These help us to analyze errors and to help you quickly.
- In SignLive! CC under Extras -> Settings -> Basic settings set the 'Log level of detail' to 'All details'.
- Then please reproduce the error again.
Then go to Window -> Show log file.
A dialog with the log files appears. - Note the dialog heading. The path to the log files is displayed there.
- Go with the Finder -> Go to -> Go to folder ... to the displayed folder and please send us all files with the ending ".log".
(The log files are usually stored under /Users//Library/Application Support/SignLiveCC_/.)
Please note that the driver software of the REINER SCT card readers may have to be updated as a result of MAC OS X updates.
If you are from Sign Live! CC click on the "Send current document" button, the file attachment is not created under Mac OS X.
This is because passing file attachments using the Mac OS X mailto protocol is not supported.
Solution:
Save file and attach later.
The card reader may be connected after the system has started, but not removed while the computer is running.
Occurs after updating MAC OS X after installing Sign Live! CC the error message "Sign Live CC.app can't be opened because Apple can't scan it for malware.", Sign Live! CC can be opened as follows:
Right-click, select Open, confirm dialog.
The libfreetype.so library, which is required for displaying a document, is no longer included in the standard deb packages for Ubuntu 12.x. The package libfreetype6-dev must be installed afterwards.
The libpcsclite library, which is required for communication with a card reader, is no longer included in the standard deb packages for Ubuntu 12.x. The package libpcsclite-dev must be installed afterwards.
You can sign in ELSTER from various applications – for example ADDISON from the company “Wolters Kluwer”.
To do this, you need PKCS#11 drivers, which we can find in Sign Live! C.C.C provide.
You can find them in Sign Live! C.C.C via menu item Tools> Settings> Libraries> PKCS # 11.
Please note:
- An RSA signature card – for example the D-TRUST – is required. Signature cards that use ECC (Elliptic curve cryptography) are not supported by this library.
- Sign Live! C.C.C is required at least version 7.1.9.
Please configure the driver directly in the application to be used.
Please note that you are alone with Sign Live! C.C.C cannot sign in ELSTER.
You are probably using a D-TRUST signature card. There are several certificates on the D-TRUST card. Among other things, a certificate for the qualified signature and one for advanced signature/authentication.
In the account query, the certificate for authentication used and therefore also requires the PIN for authentication.
If you get the error message "Incorrect PIN" when you query your account, you probably entered the PIN for signing instead of the PIN for authentication. Please note that these two PINs are usually different.
Tip:
If you entered the wrong PIN more than 3 times, it was blocked. It is also possible that this has not yet been activated in principle.
In Sign Live! C.C.C you can use the menu item Tools -> Smartcard Tools -> PIN Management initialize (put into operation) or reset (a blocked PIN) the PINs.
In both cases, please note the PIN letter from the card manufacturer.
Note:
If the PIN of a D-TRUST card has been blocked due to multiple incorrect entries, it can maximum 10x on the old PIN be reset. Therefore, please make a note of the PINs you have assigned.
If you are doing the submissions in conjunction with Addison, you can go to the signature Sign Live! C.C.C use. You can download the software from our shop at https://www.chipkartenleser-shop.de/intarsys/sign-live-cc relate.
Unfortunately, if you want to make the submissions directly to ELSTER using the Elster Authenticator, our solution is not suitable.
In this case, please contact ELSTER directly.
Tutorials
Sign Live! CC – Installation and Licensing (Win)
Download, installation and activation of intarsys software under Windows
Sign Live! CC – Installation and Licensing (Mac OS X)
Download, installation and activation of intarsys software under Mac OS X
Sign Live! CC - sign with signature card
Quick guide: Qualified signing and validation of PDF or TXT files with a signature card
Sign Live! CC – remote signature with BNotK card
Quick Guide: Remote Signature with Sign Live! C.C.C using a BNotk card
AIS Swisscom – Create TLS certificate
TLS certificate for AIS for use in Sign Live! cloud suite gears draw up
Signature cards
TELESEC: Activation of the TeleSec signature card with the "Sign Live! Toolbox Telekom Edition"
Signature cards
TELESEC: Electronic confirmation of receipt with the "Sign Live! Toolbox Telekom Edition"