Integrate Nextcloud identity attributes into the LibreSign profile

Open
#9,444 0 comments 0 reactions 0 assignees View on GitHub

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
Mostly clear
Activity status
Active
Tech stack
php

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
PHP
Stars
844
Forks
176
Avg merge
14h 3m
Merged PRs (30d)
344

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LibreSign/libresign

All issues in LibreSign/libresign

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.