Support multiple personal signing certificates per user

Open
#9,442 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
php

Research direction

Start by tracing how the account UI retrieves and deletes signature.pfx, then inspect certificate storage, authorization, migration, and lifecycle tests. The issue names no specific files or tests, so locate the existing certificate flow and its test coverage before proposing a design. Done means multiple isolated certificates, safe legacy migration, certificate-specific operations, updated UI and documentation, and passing ownership, authorization, lifecycle, and UI tests.

Written by the indexing model from the issue text.

Description

enhancement

Goal

Allow each Nextcloud account to own and manage multiple individual signing certificates, whether issued by LibreSign or imported, without certificate delegation or sharing of private keys.

Current behavior

LibreSign stores a reusable certificate as signature.pfx and retrieves it by account identifier. The current account UI assumes a single certificate. Deletion can revoke all issued certificates belonging to the account.

Confirmed requirements

  • Support multiple certificates per account, with a stable certificateId.
  • Associate each certificate with its owner, issuer and, where applicable, organizational context.
  • Support LibreSign-issued and imported PFX certificates.
  • Keep certificate material in protected storage, with searchable metadata in the database.
  • Expose subject, issuer, fingerprint, serial number, validity, source and status without reading every PFX during listing.
  • Provide certificate-specific operations for import, issuance, inspection, password change, removal and revocation where applicable.
  • Distinguish removing stored material from revoking a certificate at its issuing CA.
  • Allow one optional global default certificate per account.
  • Move certificate management from the profile header to a dedicated My certificates section.
  • Preserve existing PFX files and signing behavior through an idempotent migration.
  • Never enable delegation, shared private-key use or persistent storage of PFX passwords.

Questions to resolve

  • Final protected-storage layout and ownership model.
  • Lifecycle and availability after group membership changes.
  • Distinction between user-owned imported certificates and organization-scoped LibreSign certificates.
  • Behavior when the default certificate expires or becomes ineligible.

Done when

  • A user can independently manage multiple certificates without overwriting or revoking unrelated certificates.
  • Existing installations retain access to legacy certificates.
  • Ownership, isolation, authorization, migration and lifecycle tests pass.
  • The new UI has automated tests and reviewed visual evidence.
  • User and administrator documentation is updated.

Handoff

Before closing, review downstream certificate-selection requirements against the implemented identifiers, metadata, lifecycle and authorization contracts.

Dominant language
PHP
Stars
844
Forks
176
Avg merge
14h 3m
Merged PRs (30d)
344

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LibreSign/libresign

All issues in LibreSign/libresign

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.