Planned Support for QES / AdES Signatures and Smartcard Middleware Integration

[nascherer]

Hello DocuSeal team,

I’m currently using DocuSeal for document workflows and advanced electronic signatures (AdES) based on locally stored certificates (.p12 / .pfx).

I’d like to ask whether you are planning to support qualified electronic signatures (QES) or advanced signatures (AdES) using external qualified signature devices or middleware-based smartcard solutions — for example, access through:

smartcards such as the German electronic health professional card (eHBA) or other EU-qualified signature cards,

PKCS#11 interfaces or middleware (e.g. Open eCard Framework, Governikus Signer, Reiner SCT cyberJack),

or remote signature APIs (eIDAS compliant trust services).

At present, DocuSeal supports locally stored X.509 certificates, but there seems to be no way to interface with smartcard devices or qualified remote signature providers.

Is QES/AdES functionality (either through integration or native support) on the roadmap, or would you consider collaboration with existing open-source or certified middleware projects to achieve this?

Thank you for your great work on DocuSeal and for clarifying this point.

Best regards,
Nico Scherer

[omohokcoj]

Hi @nascherer you can learn more about how Qes or AeS works on Docuseal here:
https://www.docuseal.com/resources/sign-with-qes-or-aes
Also here is a list providers supported:
https://www.docuseal.com/faq/which-qes-and-aes-signing-methods-are-available-in-my-country
Regarding eHBA, it might be possible to use it with Trust1Connector and local certificate signing method, or integrate it with D-Trust (unfortunately we're not familiar with eHBA specificly)