Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Remember the visible signature of signers identified by email (no account)

Abierto
  • ¿Algo no está bien?
#9,249 1 comentario 0 reacciones 0 asignados Ver en GitHub

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
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
php
Área
authentication, backend

Línea de trabajo

The request describes the desired behavior and confirmation rules, but names no files, tests, or entry points. Start by reading how email identification, confirmation, and account signer signatures are currently handled. Done means an admin setting controls reuse, saved signatures are released only through the configured confirmation method, and signing or deleting updates the saved copy as described.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Is your feature request related to a problem? Please describe.

When a document is sent to a signer by email (no Nextcloud account), the signature they draw or type is only kept for the current browser session. If they close the browser and later receive another document at the same email address, they have to create their signature again.

Signers with a Nextcloud account don't have this problem: their signature is saved and offered on every document. For organisations that regularly send documents to the same external people, this means extra friction for exactly the signers who are least familiar with LibreSign.

Describe the solution you'd like

An admin setting (off by default) that lets email signers reuse their signature on later documents sent to the same address.

The saved signature should only be released through the confirm method already configured for the Email identification factor, so it's never weaker than signing itself:

  • Email token: the signer enters the emailed code to load the saved signature. The same code is then reused to sign, so they only type it once.
  • Click to sign: the valid sign link is enough, as it is for signing.
  • If both are enabled, the email token is required.

Other details:

  • The signature is saved only after the signer has passed that confirmation while signing a document.
  • Signing again with a new drawing replaces it, and deleting the signature on the signing page also forgets the saved copy.
  • On the signing page, a signer without a signature gets a "Use my saved signature" button.

I'm already working on this and have a working implementation.

Before opening a PR I'd like to know whether this feature would be welcome, and whether the approach fits the project.

Describe alternatives you've considered

No response

Additional context

A few points where I'd value the maintainers' opinion:

  1. Is a system-only setting right? Email signers have no group or user scope, so I limited it to the system scope.
  2. Is it acceptable that the signing page knows whether a saved signature exists for that email (to show the button), while the image itself is only released after the confirm method?
Lenguaje dominante
PHP
Estrellas
838
Forks
171
Merge medio
1 d 3 h
PR fusionados (30 d)
414

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de LibreSign/libresign

Todos los issues de LibreSign/libresign

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.