Be able to restrict access to all published content on non-production environments
Open
@mbiuki is already working on this.
Since Mar 14, 2025.
OKR : Customer Support
OKR : Security & Privacy
Priority : 3 Average
Team : Falcon
Type : New Functionality
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
User Story
As a dotCMS user,
I want to be able to restrict all public access to front-end content,
so I can ensure only content editors can view content on lower, non-Prod, environments
This would be immensely useful for Cloud customers.
Acceptance Criteria
Limit access to published front-end content on lower envs. This is desirable for many reasons. Occasionally this access can be limited in infrastructure but that is often not possible.
Final solution TBD. A few thoughts:
- presumably access would be limited to logged-in (backend?) users
- perhaps add an Env var that turns this feature on/off server-wide - possibly changing the default behavior of
CMS Anonymousor something like that
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
this issue has generated many support requests, and it played a role in a significant production outage
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
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.
Assessment
This issue has not been assessed yet.