nextcloud / nextcloud/server

LDAP reset user option from UI

Open
#29,469 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement feature: ldap feature: users and groups
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

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.

Is your feature request related to a problem? Please describe.
You shouldn't be obligated to use occ commands to reset an LDAP user, especially for non sysadmin peoples administrating the Nextcloud.
If your LDAP has an old user with the same dn as a new one the database keep the old and don't mark as remnant making impossible to repair this with the administration interface and the new user is unable to connect.

Describe the solution you'd like
On the user list there should be a distinction between the delete option for remnants (that crash when it's not tag as remnant) and a reset one.

Describe alternatives you've considered
Fix the delete option for LDAP user to delete the user if is a remnant or reset it else wise.

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

The issue names no files, tests, or code entry points. Start by locating the administration user list and the LDAP user/remnant handling, then trace how deletion currently behaves for stale LDAP entries. Done means administrators can distinguish reset from remnant deletion, repair the described duplicate-DN case through the UI, and have coverage for both paths.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, backend, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.