[MAGNOLIA-1696] Editing anonymous role on public instance causes all public pages to require login Created: 22/Aug/07  Updated: 23/Jan/13  Resolved: 23/Aug/07

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 3.5 RC1

Type: Bug Priority: Blocker
Reporter: zam6ak Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

3.1-SNAPSHOT
JBoss 4.0.5


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

To reproduce:

1. bootstrap fres author and public instances
2. publish /features/ to public
3. add default URI in config to have toURI: redirect:/features.html
4. edit anonymous role on public instance and add URL deny rules for /features/publishing, /features/publishing., /features/publishing/ (protecting 1 page /features/publishing.html).
5. save role
6. log out (this should take you to the features.html)

trying to access any page afterwards requires login. you don't even have to perform step #4 - just resaving the changes will cause the issue with Anonymous Context.



 Comments   
Comment by Philipp Bracher [ 23/Aug/07 ]

The tailing * where eaten by the delivered configuration.

Generated at Mon Feb 12 03:29:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.