Support multiple personal signing certificates per user
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
- Clearly specified
- Activity status
- Active
- Tech stack
- php
- Domain
- authentication, backend, database, documentation, frontend, security, testing
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- 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