Support multiple personal signing certificates per user

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start by tracing how the account UI retrieves and deletes signature.pfx, then inspect certificate storage, authorization, migration, and lifecycle tests. The issue names no specific files or tests, so locate the existing certificate flow and its test coverage before proposing a design. Done means multiple isolated certificates, safe legacy migration, certificate-specific operations, updated UI and documentation, and passing ownership, authorization, lifecycle, and UI tests.

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

描述

enhancement

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.

主要语言
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 摘要。