Skip to content

Support multiple personal signing certificates per user #9442

Open
0 of 2 issues completed
Open

Description

@vitormattos

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions