[MAGNOLIA-1293] Role ACL is ignored on public instance Created: 04/Jan/07 Updated: 23/Jan/13 Resolved: 19/Apr/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 3.1 M1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Robert Gacki | Assignee: | Sameer Charles |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
+ JDK 5.0_10 |
||
| Issue Links: |
|
||||||||
| 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 |
|
Prerequisites: Bug: My proposal: |
| Comments |
| Comment by Sameer Charles [ 04/Jan/07 ] |
|
when you said "anonymous" user is not logged in by default on public instance in report once |
| Comment by Magnolia International [ 04/Jan/07 ] |
|
reopening, since its not really "resolved" yet |
| Comment by Robert Gacki [ 04/Jan/07 ] |
|
Yes, JIRA does all that. Meanwhile, I tested another situation. I simply created a new user and assigned the 'anonymous' role to this one. If it is just a dependency (and solved by the root issue), Content#isGranted( Permission.READ ) should have returned FALSE for page '/two' now, but it does not. No offence Sameer, but this looks much more than a dependency to me. If I can spend some time on it in my weekend, I'll dig into it, too. |
| Comment by Sameer Charles [ 04/Jan/07 ] |
|
ok my mistake, I should have linked this task!! Now, what you are saying means that none of the access control works, anonymous user / role is no exception perhaps you are using wrong context to obtain content objects. |
| Comment by Robert Gacki [ 04/Jan/07 ] |
|
In the jsp fragment, which creates my navigation I do: Content activePage = Resource.getCurrentActivePage( (HttpServletRequest) pageContext.getRequest() ); Then I use the rootPage to iterate on the branches (rootPage.getChildren()). Each child is checked for read permission: if( !child.isGranted( info.magnolia.cms.security.Permission.READ ) ) Am I wrong with this? I learned from the taglibs how to access content in a programmatic way. |