Integrate Nextcloud identity attributes into the LibreSign profile

Aperta
#9,444 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
php

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
PHP
Stelle
844
Fork
176
Merge medio
14h 3m
PR unite (30g)
344

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di LibreSign/libresign

Tutte le issue di LibreSign/libresign

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.