Select and authorize signing certificates by request context
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- php
- Domain
- authentication, backend-api-design, security
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- PHP
- Stars
- 844
- Forks
- 176
- Avg merge
- 14h 3m
- Merged PRs (30d)
- 344
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LibreSign/libresign
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
OpenSSL engine: leaf certificates get O=Internet Widgits Pty Ltd, ST=Some-State from system openssl.cnfPossibly taken @vitormattos claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LibreSign/libresign#9366 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
LibreSign/libresign#9007 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LibreSign/libresign#8284 · 5 comments ·
Maintainers usually reply within 1 day
-
frontend javascript technical debt
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
All issues in LibreSign/libresign
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Automattic/blocks-engine#6318 ·
Maintainers usually reply within 1 day
-
[remove-resource] Delete Open Course Hub, Open Multicourse Hub, and Learn2 with GitSync skeletonsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
35-feedback
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day