nextcloud / nextcloud/richdocuments
When builtin is detected, default to loopback only for the WOPI allow list
Open
Nobody has claimed this yet.
0. Needs triage
enhancement
feature: settings
integration: built-in code server
setup
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
There is no reason I see - when used with builtin CODE - to leave the default WOPI allow list empty/open (requiring it to be manually configured).
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
No file or test is named in the issue. Start by locating the builtin CODE detection and the WOPI allow-list default handling, then verify how manual configuration is preserved. Done means builtin CODE defaults the allow list to loopback only while non-builtin setups and explicit settings retain their current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100