Integrate Nextcloud identity attributes into the LibreSign profile

Abierto
#9,444 0 comentarios 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
php

Línea de trabajo

Start by reading the account settings API wrapper for updating the phone number and how LibreSign currently uses Nextcloud's IAccountManager. Then review Nextcloud's account APIs, access controls and visibility semantics to resolve the property allowlist, editability and API approach. Done means supported attributes display consistently, approved edits persist through authorized Nextcloud APIs, privacy and permission tests pass, and certificate attributes are reviewed against the property contract.

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

Descripción

enhancement

Goal

Improve the LibreSign account profile by reusing relevant identity attributes already maintained by Nextcloud, without creating an unnecessary duplicate user directory.

Current behavior

LibreSign already uses Nextcloud's IAccountManager; the account settings API currently includes a wrapper for updating the phone number. Certificate management occupies space in the user profile.

Confirmed requirements

  • Display relevant Nextcloud account properties such as display name, email, phone, organization, role and address where available.
  • Evaluate which properties should be editable from LibreSign.
  • Reuse Nextcloud's account APIs, access controls and visibility semantics.
  • Use backend authorization for reads and writes; frontend visibility alone is insufficient.
  • Keep Nextcloud as the source of truth for normal account properties.
  • Avoid unnecessary duplication or synchronization tables.
  • Support a focused identity profile while certificate management moves to its dedicated section.
  • Do not infer structured country, state or city from unstructured address text without an explicit verified transformation.
  • Distinguish user-declared and verified properties where Nextcloud exposes that information.

Questions to resolve

  • Exact property allowlist and editability.
  • Whether a LibreSign API wrapper improves consistency over directly linking to native Nextcloud settings.
  • How visibility scopes should be represented without duplicating privacy controls.
  • Which attributes are useful to future certificate issuance policies.

Done when

  • Users can view supported identity attributes consistently in LibreSign.
  • Approved updates are persisted through supported Nextcloud APIs.
  • Privacy, ownership and permission tests pass.
  • No redundant identity record becomes a competing source of truth.
  • The profile UI is responsive, accessible and documented.

Handoff

Before closing, review the certificate-attribute epic against the implemented property contract, including value origin, visibility and verification status.

Lenguaje dominante
PHP
Estrellas
844
Forks
176
Merge medio
14 h 3 min
PR fusionados (30 d)
344

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.