Manage multiple certificate authorities by organizational context

未关闭
#9,443 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
php

调研方向

Start by reading the existing policy infrastructure and the code for CA configuration, certificate issuance, key storage, and CRL routing; the issue does not name specific files or tests. Map how issuer identity and organizational context flow through those paths before proposing an implementation. Done means multiple CAs operate with context isolation, legacy certificates and CRL URLs remain valid, and the specified authorization and revocation tests and documentation are complete.

由索引模型根据 Issue 内容生成。

描述

enhancement

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.

主要语言
PHP
星标
844
派生
176
平均合并
14 小时 3 分钟
30 天内合并 PR
344

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

LibreSign/libresign 的其他 Issue

查看 LibreSign/libresign 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。