How to make private staging not exposed publicly in the catalog
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 1
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 18
Description
Once https://github.com/openzim/cms/issues/399 is implemented, unauthorized users will not have access to private collections anymore. There is however still one very public API: the library.xml of staging area.
This is very strongly related to the fact that ATM we have only one Kiwix-serve to expose the whole staging area (to be solved in https://github.com/kiwix/operations/issues/664).
We will probably have to move https://github.com/kiwix/operations/issues/664 and this issue forward at the same time, this is more a placeholder issue at this stage to not forget about this topic.
Contributor guide
No contributing guide indexed for this repository
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 reading this issue together with cms#399 and operations#664, then inspect how the staging area is exposed through Kiwix-serve and how its library.xml remains publicly available. Coordinate the work with operations#664; done means unauthorized users cannot access private staging collections through the catalog API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100