Skip to content
All technical docs Bricks technical documentation

eIDAS: identification and signatures

How BricksID identifies people and lets them sign, measured against the eIDAS regulation as it applies today: the signature level offered, the evidence and its seal, long-term verification, and what is not offered yet.

eIDAS: identification and signatures

Bricks Technical Documentation

How BricksID identifies people and lets them sign, measured against the eIDAS regulation as it applies today: the signature level offered, the evidence and its seal, long-term verification, and what is not offered yet.


This page covers the eIDAS regulation (EU) 910/2014 as it applies today. What the 2024 revision adds, the European Digital Identity Wallet, is covered in eIDAS 2. The integration protocol is in BricksID.

Identification

People sign in to every app on Bricks with one BricksID, through standard OpenID Connect.

  • An email address is proven by following a link sent to it.
  • A second factor (an authenticator app or a code by email) can be turned on by the person; once on, every request of a session that has not passed it is refused.
  • Accounts are named: signing up asks for a first and a last name. They are declared by the person, not verified.

Current limits. BricksID does not yet verify identity against an official document or means (eID card, itsme): a BricksID account proves control of an email address and, when turned on, of a second factor, not a civil identity. Identification is therefore not yet at an eIDAS assurance level.

Art. 25 — Simple electronic signature

A person signs a document in an organisation's app through BricksID. This is a simple electronic signature: art. 25 makes it admissible as evidence, and its weight is argued from the evidence kept. The product never presents it as advanced or qualified, on the signing page or in the person's list.

  • The signature belongs to the person. The original document, the signed document and the evidence are kept in the person's BricksID; the organisation that asked receives them.
  • Only the person signs. The organisation cannot sign for them, and neither can someone representing them under a mandate.
  • The person reads, then signs. Their handwritten signature, set once, is placed on the document.

The evidence and its seal

When the person signs, the platform writes the evidence and seals it in the same step; nothing is recorded as signed without its seal. The evidence states:

  • what was signed: a fingerprint of the original and of the signed document;
  • who signed, whether their email address was proven and whether they use a second factor;
  • which organisation and app asked, and when it was asked and signed.

The seal is made with a key of the platform kept for this purpose alone. It is an electronic seal of Bricks, not a qualified electronic seal (art. 35 and 36).

Long-term verification

  • Anyone holding the evidence can check it without an account, against the platform's published public keys, and learn whether a given file is the original or the signed document.
  • Published keys are never deleted. A key that is replaced gets an end date, so evidence sealed today still verifies years later.

Current limits. The signed PDF shows the handwritten signature; the evidence travels beside it as a separate file, not as a signature embedded in the PDF that a PDF reader checks. No qualified timestamp is applied.

Advanced and qualified signatures

Current limits. BricksID does not yet offer advanced (art. 26) or qualified (art. 25(2)) electronic signatures, and does not yet sign with a qualified certificate from a qualified trust service provider. One signer per request.