Select and authorize signing certificates by request context

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start by identifying the certificate inventory and issuer/context contracts; the issue says implementation depends on those integrations, but names no files, tests, or entry points. Resolve the listed policy and lifecycle questions before implementation. Done means request policy controls eligible certificate choices, backend checks block prohibited signing, and automated integration and browser tests cover eligible, ambiguous, and prohibited selections while existing signed PDFs remain valid.

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

描述

enhancement

Goal

Automatically suggest and securely authorize the appropriate personal signing certificate for each signature request, considering its organizational context and the signer's eligible certificates.

Confirmed requirements

  • Associate signing requests with a backend-validated organizational context when applicable.
  • Preserve the relevant context and resolved policy across the signing lifecycle.
  • When a request belongs to organization A, prefer an eligible certificate associated with A.
  • When a request belongs to organization B, prefer an eligible certificate associated with B.
  • Support users belonging to multiple groups and owning multiple certificates.
  • Allow manual selection among certificates permitted by the request policy.
  • Allow certificates from another organization or external issuer only when explicitly permitted.
  • Support one optional global default certificate per user without overriding context-specific eligibility.
  • Prompt for selection when multiple eligible certificates remain and no unambiguous default exists.
  • Handle missing, expired, revoked, disabled and inaccessible certificates.
  • Prevent unauthorized cross-context use through backend checks, including immediately before signing.
  • Preserve the distinction between persistent certificates and temporary Click to Sign certificates.
  • Record the effective certificate and issuer used for signing without exposing private keys or passwords.
  • Preserve validation and auditability of previously signed documents.

Questions to resolve

  • Which event establishes the organizational context of a signing request.
  • Whether the context may differ for individual signers in the same request.
  • Handling an external signer who is not a member of the requesting organization.
  • The precise eligibility rules for imported certificates.
  • The treatment of group membership changes after a request is created.
  • Recovery and UX when no eligible certificate exists.

Planning gate

Implementation depends on the certificate inventory and issuer/context contracts. UX prototypes and simulated contract tests may proceed before those integrations are available.

Done when

  • Certificate selection is predictable for multi-group users.
  • Request policy determines eligibility; frontend choices cannot bypass it.
  • Temporary, imported and persistent certificate flows remain functional.
  • Automated integration and browser tests cover eligible, ambiguous and prohibited selections.
  • Existing signed PDFs remain valid and signing documentation is updated.
主要语言
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 摘要。