nextcloud / nextcloud/ldap_contacts_backend

LDAP backend to support sync of user manager data to NextCloud users

Open
#306 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
PHP
Stars
9
Forks
7
Avg merge
1d 13h
Merged PRs (30d)
25

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Feature request

Which Nextcloud Version are you currently using: 31.0.5

Is your feature request related to a problem? Please describe.
I have to maintain Contacts org chart separately to the data available in OpenLDAP because there is no mapping for manager available.

Describe the solution you'd like
I would like to centrally manage user/contact Manager mappings in LDAP only and have it sync to NextCloud so that it shows in the Org chart correctly.

Describe alternatives you've considered
I could pull the LDAP user and manager data down to the NextCloud server and store in a file on disk, then call the occ command to automatically update the user manager field.

Additional context
N/A

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the LDAP attribute-mapping and user synchronization entry points in the ldap_contacts_backend repository, then trace how Nextcloud user manager data is stored and exposed to the Contacts org chart. The work is done when manager mappings can be maintained in LDAP, synchronized to Nextcloud users, and shown correctly in the org chart.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.