Manage multiple certificate authorities by organizational context

オープン
#9,443 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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分
マージ済み PR(30日)
344

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

LibreSign/libresign のほかの issue

LibreSign/libresign の issue をすべて見る

似ている issue

PHP の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。