Skip to content

Introduce a CA registry with stable issuer identity and legacy compatibility #9475

Open

Description

@vitormattos

Goal

Establish the backend registry and identity contract needed to manage multiple certificate authorities in one LibreSign installation.

Current state

The active CA is represented by application-level configuration and identifiers used throughout certificate issuance and CRL services.

Scope

  • Define a persistent CA record with an opaque public issuer identifier.
  • Represent CA identity, engine type, generation, lifecycle state and protected storage references.
  • Preserve the existing installation's CA without regeneration or certificate reissuance.
  • Support more than one registered CA, while leaving policy-based selection and administration UI for subsequent work.
  • Define how organizational contexts may reference a CA without using the Nextcloud group ID as its cryptographic identity.
  • Establish the identifier contracts needed by issuance, certificate inventory, revocation and CRL distribution.
  • Keep historical instanceId, generation and engineType information available for compatibility.
  • Define and verify the issuer-scoped identity of certificates, including cases where different issuers use the same serial number.
  • Establish backend ownership and authorization boundaries for privileged CA operations.

Acceptance criteria

  • Legacy CA configuration can be represented in the registry without changing its keys or issued certificates.
  • Multiple CA records have stable, unambiguous issuer identifiers.
  • A CA can be referenced independently of a group's name or lifecycle.
  • Missing or unauthorized issuer references fail safely.
  • Tests cover registry isolation, legacy compatibility, identity collisions and invalid issuer lookup.
  • Existing CRL URLs and certificate validation behavior remain unchanged.
  • The CA registry contract is documented for subsequent implementation.

Out of scope

New CRL routes, complete multiple-CA issuance, group administration UI, delegated CA creation and changes to signer certificate subject policies.

Handoff

Review the multi-CA epic's remaining implementation requirements against the registry contract before opening detailed CRL, provisioning and policy-selection issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendBackend workenhancementApp improvimentsphpWork involving PHP code

    Type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions