Skip to content

Manage multiple certificate authorities by organizational context #9443

Open
1 of 2 issues completed
Open

Description

@vitormattos

Goal

Allow a single LibreSign installation to manage multiple certificate authorities (CAs) and associate them with organizational contexts through the existing policy system.

This enables distinct certificate issuers for SaaS customers without equating a Nextcloud group identifier with the cryptographic identity of a CA.

Current behavior

The active CA is identified primarily through instance-level configuration. Certificate issuance, private-key storage and CRL handling are not yet designed around a registry of independent issuers.

Confirmed requirements

  • Register multiple CAs with stable, opaque public identifiers.
  • Preserve issuer identity, key generation and certificate engine (OpenSSL or CFSSL).
  • Maintain compatibility with the existing single-CA configuration and certificates.
  • Associate CAs with groups and organizational contexts without exposing group names in public CRL paths.
  • Support system-wide defaults and group-scoped CA selection through existing policy infrastructure.
  • Allow the system administrator to delegate specific CA administration capabilities.
  • Separate policy configuration from privileged CA operations, key custody and rotation.
  • Keep CA private keys protected; do not expose raw private-key export as an ordinary group administration feature.
  • Maintain correct CRL generation, distribution, caching and revocation for each issuer.
  • Preserve historical CRL URLs and validation of existing certificates.
  • Identify revocation records by issuer and serial number rather than treating serial numbers as globally unique.
  • Handle users belonging to multiple groups without ambiguous implicit issuer selection.

Initial architectural direction

Use independent CA identities with explicit associations to organizational contexts. Keep engineType as part of CRL routing. Start with independently managed roots; evaluate intermediate-CA hierarchies separately if a demonstrated need arises.

Questions to resolve

  • Whether one context may authorize several CAs.
  • Provisioning, rotation, disablement and eventual retirement of a CA.
  • Exact delegated operations available to group administrators.
  • Migration of legacy issuer, storage and CRL metadata.
  • Isolation boundaries in a shared SaaS process.

Done when

  • Multiple issuers can coexist and operate without cross-context certificate or key access.
  • Policies determine CA eligibility through backend-validated contexts.
  • Revocation and validation remain correct for new and historical certificates.
  • Cross-engine, cross-context and negative authorization tests pass.
  • CA administration and migration are documented.

Handoff

Before closing, reconcile downstream subject-attribute and signing-selection epics with the actual issuer identity, organizational-context and authorization contracts.

Activity

  1. added theissue type on Nov 12, 2026
  2. no84by commented on Nov 18, 2026

    @no84by

    A related case from production use: one installation serving two organizations, each with its own organization seal certificate issued by an external CA (not by LibreSign). Each request chooses which organization seals it: one, the other, or both.

    #9553 (issue #9547) implements that part: seal certificates registered with stable opaque ids and a label, selected per request through the policy system, applied after the last signature. It does not issue certificates or handle CRLs, so it does not replace this epic.

    Question for the registry design in #9475: should externally issued organization seal identities live in the same registry as LibreSign-operated CAs (as a "custody only, no issuance" kind), so organizational context selects both from one place? If yes, #9553 can be adapted to that contract.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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