Repository navigation
Description
This is a roadmap and funding epic.
Important
Do not implement this epic directly.
This issue exists to define the next architecture step after #8335 and to make the work visible for organizations that may want to fund it.
If you are interested in this topic, discussion is welcome. Implementation should happen only through focused child issues after the architecture and scope are defined.
Background
#8335 creates the foundation for signing when the private key is outside LibreSign.
The next step is to add a provider layer around that foundation.
LibreSign should be able to work with remote signing services without putting provider-specific API, authorization or session logic inside the PDF/PAdES signing layer.
Goal
Create a provider-independent architecture for remote signing.
The provider layer should be able to handle concerns such as:
- provider discovery and configuration;
- credential selection;
- authorization flows;
- signing session lifecycle;
- sending prepared signing data to a provider;
- receiving the returned signature value;
- provider-specific errors and retry behavior.
The PDF/PAdES layer must remain independent from these details.
Why this matters
This is the bridge between the generic external-signing foundation and real remote signing services.
A common provider architecture allows LibreSign to support different ecosystems without creating a separate signing implementation for each one.
Possible future integrations include:
- Cloud Signature Consortium (CSC);
- European trust service providers;
- ICP-Brasil PSC;
- cloud KMS and HSM-backed services;
- other remote signing APIs.
This also makes the work easier to fund because each protocol or provider can be implemented as an isolated follow-up project.
Expected direction
The architecture should keep this separation:
LibreSign workflow
|
v
PDF / PAdES signing layer
|
prepare / complete
|
v
Remote signing provider layer
|
v
Provider API / trust service / HSM service
The provider layer must not need to understand PDF structure, ByteRange or incremental PDF updates.
Out of scope
This epic does not implement:
- CSC itself;
- eIDAS/QTSP integration;
- ICP-Brasil PSC;
- local smart cards or tokens;
- PKCS#11;
- a specific commercial provider.
Those should be separate follow-up epics.
Funding opportunity
This work is suitable for organizations that need vendor-independent remote signing in LibreSign.
Funding this epic would create reusable infrastructure instead of a one-off integration for a single provider.
Dependency
This epic depends on the external signing foundation in #8335 being sufficiently stable.
Done when
This epic is ready to be closed when the provider architecture has been implemented through focused child issues and at least one provider can use it without adding PDF/PAdES logic to the provider integration.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Projects
- StatusShow more project fieldsNo status
Activity
[-][EPIC] Add remote signing provider architecture[/-][+]Add remote signing provider architecture[/+]