Select and authorize signing certificates by request context
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- php
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- PHP
- Estrellas
- 844
- Forks
- 176
- Merge medio
- 14 h 3 min
- PR fusionados (30 d)
- 344
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de LibreSign/libresign
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
OpenSSL engine: leaf certificates get O=Internet Widgits Pty Ltd, ST=Some-State from system openssl.cnfPosiblemente ocupada @vitormattos la tomó hace 5 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
LibreSign/libresign#9366 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 83/100
LibreSign/libresign#9007 · 2 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
LibreSign/libresign#8284 · 5 comentarios ·
Los mantenedores suelen responder en 1 día
-
frontend javascript technical debt
Dificultad 5/5 Más de una semana Aptitud para principiantes 8/100
Los mantenedores suelen responder en 1 día
Todos los issues de LibreSign/libresign
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
Automattic/blocks-engine#6318 ·
Los mantenedores suelen responder en 1 día
-
[remove-resource] Delete Open Course Hub, Open Multicourse Hub, and Learn2 with GitSync skeletonsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
-
Allow @ in the service nameAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
-
35-feedback
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día