The overall project structure has been derived from the high level design of the Open eCard App (see [[Sicherheit 2012 submission) and is depicted in the following figure:
The following modules are derived from the high level project structure.
Information about the architecture, data structures and other things can be found in the respective links.
Contains web service definitions (.xsd, .wsdl) and related utilities.
Contains common utilities and helper classes.
Contains basic crypto modules.
Contains the functionality for [[SAML-ECP]].
Contains signature-related functionality.
Contains modules related to the transport of messages.
Contains user interfaces (User Consent) for the different platforms.
Contains the interface device (IFD) components for the different platforms. The following figure provides an overview of the relationship between the different ifd modules:
EstablishChannel
. Currently the following protocols are supported:
Contains the service access layer (SAL) components.
Features CardInfo-based card type recognition. This module also bundles CardInfo files for the recognisable cards.
Provides an easy to use interface for IFD related events.
Contains components for the integration of the Open eCard App into popular browsers.
This module is used to activate the client and authenticate against a server.
The eCard-API Framework part 7 defines the TCToken-Interface to trigger the activation.
More sophisticated activation scenarios need the possibility to request information about the App and available token. The Status-Interface extends the TCToken-Interface respectively.
Contains modules for the different forms of the Open eCard App.