open-ecard  2.1.2
About: Open\
About: Open eCard provides a simple and homogeneous interface to enable standardised use of the various smart cards (especially of the German eCard-API-Framework) for different applications. 2.x series.
provides a simple and homogeneous interface to enable standardised use of the various smart cards (especially of the German eCard-API-Framework) for different applications. 2.x series.
  Fossies Dox: open-ecard-2.1.2.tar.gz  ("unofficial" and yet experimental doxygen-generated source code documentation)  

open-ecard Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies open-ecard-2.1.2.tar.gz contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).

About Open eCard and MOBILE-X

The Open eCard project was started in 2012 by industrial and academic experts to provide an open source and cross platform implementation of the eCard-API-Framework (BSI TR-03112) and the related international standard ISO/IEC 24727, through which arbitrary applications can utilize electronic identification (eID), authentication and signatures with suitable smart cards (eCards). In a high-level perspective the architecture of the eCard-API-Framework consists of the following layers:

  • Application-Layer
  • Identity-Layer
  • Service-Access-Layer
  • Terminal-Layer

Against the background of the eIDAS-Regulation, the General Data Protection Regulation (GDPR), the GAIA-X initiative and the ongoing trend towards increased mobility, the Identity-Layer has been subject to an ongoing revision to form MOBILE-X, which integrates the ChipGateway protocol as well as aspects of Identity Management ISO/IEC 24760 and Privacy Management ISO/IEC 29101 in order to enable electronic signatures and "Self Sovereign Identity".

The artifacts of the project consist of modularized, and to some extent extensible, libraries as well as client implementations such as a Desktop application (richclient) an smartphone apps for Android and iOS.

Build Instructions

Detailed build instructions can be found in the file bundled with this source package.

Quick Start

The simplified build instructions are as follows:

$ git clone git://
$ cd open-ecard
$ mvn clean install

In case you received a preassembled source bundle, the build instructions are as follows:

$ tar xaf open-ecard-${version}.tar.xz
$ cd open-ecard-$version
$ mvn clean install

Finally, you can run the Open eCard App from command line:

$ ./packager/richclient-packager/target/open-ecard/bin/open-ecard


Native packages which are based on a modular runtime image can be built with the new jpackage tool which is a candidate for JDK-14. Early-access builds are already provided. Native packages for the Open eCard can be built by downloading the JDK-14 early-access build, referencing it as toolchain and by specifying the following property:

$ mvn clean install -Ddesktop-package

By default, the packager will take the predefined package types, such as dmg for Mac OS and deb for Linux-based systems. The package type can be overridden for Mac and Linux packages by using the following user property:

$ mvn clean install -Ddesktop-package -Djlink-jpackager.package-type=<type>

Thereby, the following types are available:

  • dmg
  • pkg
  • deb
  • rpm

You have to make sure the required packaging tools are installed. In case of Windows, msi and exe packages are built. For this purpose, two additional tools are required:

  • WiX toolset - to create msi installers
  • Inno Setup - to create exe installers (Path environment variable must be set)

More information about the required JDK versions and the setup of the toolchain, can be found in the file.

Mobile libs

Open eCard supports building of libraries for Android and iOS for usage in arbitrary mobile apps.


After a successfull build the library for android can be found in android-lib sub project. It also can be used as prebuild dependency via gradle dependency management. See open-ecard-android for further information.

iOS (>2.x)

If building on MacOS a ready to use framework gets generated and can be found in ./packager/ios-framework/target/robovm.
The framework can also be found as asset of the release.

It also can be installed as a cocoapod dependency.

pod 'open-ecard'

See open-ecard-ios for further information.


The Open eCard App uses a Dual Licensing model. The software is always distributed under the GNU General Public License v3 (GPLv3). Additionally the software can be licensed in an individual agreement between the licenser and the licensee.


New developers can find information on how to participate under

Contributions can only be accepted when the contributor has signed the contribution agreement ( The agreement basically states, that the contributed work can, additionally to the GPLv3, be made available to others in an individual agreement as defined in the previous section. For further details refer to the agreement.