Change LDAP's "Clear mappings" to follow standard delete routines
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
To avoid leaving garbage in the filesystem or database and preventing potential issues as fixed with #11383.
This should not cause difficulties, as it is adviced not to do it in the production stage. Since it is a fundamental change, this need to be communicated properly and clearly and should also be extended with a password confirmation.
cc @MorrisJobke
Contributor 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.
Research direction
Start by locating the LDAP “Clear mappings” entry point and compare its behavior with the standard delete routines referenced by the issue. Read issue #11383 for the related fix and identify the existing confirmation flow. Done means the LDAP action avoids leaving filesystem or database garbage, requires password confirmation, and is clearly communicated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100