Add clear documentation in guides about blocking crucial API endpoints from the outside
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Check and highlight for production setups in classic and/or containerized installations:
- Block /api/admin and /api/builtin-users in Dataverse with a policy
- Block these endpoints on the Reverse Proxy as well
Provide example snippets for this for Apache and NGINX (classic installations) as well as Traefik (Docker) and Ingress, Gateway API (Kubernetes).
This should be done in the Installation and Containerization Guides.
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 with the Installation and Containerization Guides and identify the sections covering classic and containerized production setups. Add example policies and reverse-proxy configurations for /api/admin and /api/builtin-users using Apache, NGINX, Traefik, Ingress, and Gateway API. Done means both guides clearly explain blocking these endpoints and include examples for each requested deployment style.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, docker, kubernetes, nginx
- Domain
- devops, documentation, infrastructure, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100