Integrate Nextcloud identity attributes into the LibreSign profile
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
- Domain
- authentication, full-stack
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
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
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LibreSign/libresign
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
OpenSSL engine: leaf certificates get O=Internet Widgits Pty Ltd, ST=Some-State from system openssl.cnfPossibly taken @vitormattos claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LibreSign/libresign#9366 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
LibreSign/libresign#9007 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LibreSign/libresign#8284 · 5 comments ·
Maintainers usually reply within 1 day
-
frontend javascript technical debt
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
All issues in LibreSign/libresign
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Automattic/blocks-engine#6318 ·
Maintainers usually reply within 1 day
-
[remove-resource] Delete Open Course Hub, Open Multicourse Hub, and Learn2 with GitSync skeletonsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
35-feedback
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day