Skip to content

Add Cloud Signature Consortium (CSC) support #8943

Open

Description

@vitormattos

This is a roadmap and funding epic.

Important

Do not implement this epic directly.

This issue is used to define, discuss and fund CSC support in LibreSign.

Implementation should be split into focused child issues after the external-signing and remote-provider foundations are ready.

Background

LibreSign is moving toward a signing model where the private key does not need to be available inside the application.

Cloud Signature Consortium (CSC) provides an open API model for remote signing services and is a natural next step after the generic external-signing and provider foundations.

Goal

Allow LibreSign to use CSC-compatible services for remote digital signatures.

The integration should keep CSC-specific communication outside the PDF/PAdES layer.

Expected scope

The final implementation is expected to cover the parts of CSC needed for a complete LibreSign signing flow, including topics such as:

  • service and credential discovery;
  • credential selection;
  • authorization;
  • signing operations;
  • signing session lifecycle;
  • handling returned signature values;
  • error handling;
  • interoperability tests with independent CSC implementations.

The exact CSC API version and endpoint coverage must be defined before implementation starts.

Why this matters

CSC gives LibreSign a standards-based path to cloud and remote certificates without creating a custom integration for every signing provider.

This is also important for future support of European trust services, because CSC is used by remote signing services in that ecosystem.

The same architecture can remain useful outside Europe and can coexist with other protocols such as ICP-Brasil PSC.

Business and funding value

Organizations often need to keep certificates and private keys in managed trust services, HSM-backed services or cloud signing platforms.

Funding CSC support would add a reusable open integration to LibreSign instead of tying the project to one vendor.

Organizations that operate CSC-compatible services, use remote certificates or need integration with trust service providers are good candidates to fund or validate this work.

Dependencies

This epic depends on:

Out of scope

This epic should not:

  • turn LibreSign into a trust service provider;
  • implement provider-specific proprietary APIs unless required as a separate adapter;
  • put CSC logic inside the PDF/PAdES engine;
  • cover local smart cards or USB tokens.

Done when

LibreSign can complete a digital signing workflow using a CSC-compatible service while keeping the private key outside LibreSign, with automated interoperability and regression tests.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions