ownCloud shares are removed temporarily when LDAP server is not available
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 17
- Forks
- 19
- Avg merge
- 11h 40m
- Merged PRs (30d)
- 2
Description
Today I needed to reboot my LDAP server. The reboot caused the LDAP connection to be broken, but what made matters worse is that shares created by LDAP users are removed for non-LDAP enabled accounts.
Consider this setup:
- User
Ais authenticated against LDAP - User
Bhas a normal ownCloud account - User
Ashares a directoryDto userB - User
Bsyncs using his or her ownCloud client ,Dis downloaded - The LDAP server is rebooted, hence the connection is lost and
Ais unable to authenticate - The ownCloud client of user
Bnotifies the user thatDhas been unshared and deletesDfrom disk - LDAP server comes back online
- Shares are restored
- User
Bneeds to redownloadD
The problem is that D contains about 20 GB of files, and these 20GB are added to our allotted network bandwidth. Consider you need to reboot LDAP quite often, it always causes those 20GB to be deleted and redownloaded a couple of minutes later.
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
The issue names no files, tests, or entry points. Start by reproducing the described LDAP outage with an LDAP user sharing a directory to a local user, then trace what happens to the share while LDAP is unavailable. Done means the local user's share is not removed and does not trigger a delete and redownload when LDAP returns.
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
- 30/100