Whitelisting too strict on public links
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 61
- Forks
- 34
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 22
Description
A bunch of apps like for example Talk, Forms or Appointments allow creating public links.
When a guest user opens a public link while they are currently logged into the respective Nextcloud instance, the whitelisting (or in this case blacklisting) kicks in and doesn't show the content (except of course if the app is explicitly whitelisted).
The only working thing are public file links.
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 a public link from Talk, Forms, or Appointments while logged in, compare it with a public file link, and trace the guest-user whitelisting or blacklisting path; done means the affected public links show their content without breaking file links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100