DATA Sign Cookbook

This repository gives guidance on integrating DATA Sign into your application.

The DATA Sign Integration Guide is - next to this repository - a good starting point for developers to familiarize themselves with the DATA Sign REST API. The Integration Guide can be accessed from the Governikus Portal.

The examples here are plain Java code and demonstrate the REST API usage. The examples are implemented with the following simplifications:

• we make no use of client code generation from our OpenAPI specification document, although it's possible (the OpenAPI specification can be access from the Governikus Portal)
• most error handling is omitted

For our to-be-signed based endpoints your application must perform low level signature operations (e.g. calculating the DTBS). For this purpose our examples make use of the European Union Digital Signature Service library.

Prerequisites

• Java 17
• Maven
• Either access to our publicly hosted DATA Sign test instance (ask your Governikus contact person) or your own running DATA Sign and Keycloak instance.
• For Signing examples a registered and identified user account of one of the supported providers
• For Sealing examples a server-side configured test seal from one of the supported providers
• A configured cookbook.properties file (copy it from cookbook.properties.template), see the table below

cookbook.properties key	Description
url	API url, e.g. https://api.your-datasign.test/
keycloak.issuerUri	The Keycloak realm url, same as server-side configured, e.g. https://your-keycloak/realms/your-realm
keycloak.clientId	The Keycloak Client ID
keycloak.clientSecret	The Keycloak Client Secret
example.provider	Your chosen provider, e.g. "Bank-Verlag" BV or "D-Trust" DTRUST
example.userId	ID (e-mail address) of a registered and identified user account of your chosen provider. Only required for signing examples.
example.sealId	A server-side configured seal of your chosen provider. Only required for sealing examples.

Run the examples

Each example can be executed on its own (see main method). All IDEs should be able to run the example classes directly.