The functionality of MOA SP and MOA SS can be called both via the Web service interface (SOAP) as well as via an API. The Web service interface provides the possibility for clean separation of the calling application and the MOA components. Together with the multi-client capability of the design, this also offers the possibility of operating MOA centrally for multiple applications. In the specification, general requirements such as platforms, authentication, scalability, availability, logging, namespaces as well as the command format are defined.
Using the MOA-SS and MOS-SP modules:
- Efficient service. Documents can be electronically signed in a customer friendly way, independent of the time and place, and legally and subsequently sent to the desired recipient over the Internet within seconds.
- Easy use of the digital signature on electronic documents as a modern alternative to a handwritten signature on paper documents.
- The origin and authenticity of electronically signed documents from government agencies that are sent over the Internet can be verified in an easy way. Forged documents can be recognised immediately, because the electronic signature is invalid.
The MOA-SP module encapsulates the entire functionality of the server-side signature verification, which applications need in connection with the use of Citizen Cards. Both signatures that conform to the Citizen Card specification as well as signatures that satisfy the XAdES / XMLDSig, CAdES / CMS, and PAdES standards are supported. They can be simple or qualified signatures. The query and reply mode is orientated around the commands of the Citizen Card specification. The interface consists of XML-based query and reply messages. The related XML schema is described in the MOA schema, which is contained in the specification suite. MOA-SP supports the XAdES, CAdES, and PAdES formats defined as a minimum in connection with the service guideline in a cross-border exchange.
The base module MOA-SS encapsulates the entire functionality of the server-side signature creation. Signatures that conform to the Citizen Card specification and also signatures in accordance with the XAdES B-Level / XMLDSig Standard or CAdES B-Level / CMS Standard can be created. Creation is possible with software keys, but hardware security modules (HSM) are also supported. The process is broken down into the determination of the signature key, resolution of the data to be signed, calculation of the transformations and creation of the signature. Batch signatures can be carried out. In the process, multiple signatures are created with one command for multiple documents.
The software releases can be found on joinup. Documentation is available on apps.egiz.gv.at (German only).