[MAGNOLIA-1054] exception raised if user tries to access a not permitted property Created: 14/Sep/06 Updated: 23/Jan/13 Resolved: 15/Sep/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.0 RC2 |
| Fix Version/s: | 3.0 RC3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Chris Miner | Assignee: | Boris Kraft |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 10m | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | 10m | ||
| Attachments: |
|
| 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 |
|
I sett up a security role that denied access to: /*/title intending to test if this would deny me access to that property. That worked, I can no longer see titles anywhere. But the log file shows a stack trace and a warning. I looked into the stack trace and found it is printed out in getNodeData on Content. In this method the WARNING worthy unexpected RepositoryException catches the benign and from time to time expected AccessDeniedException as well. Attached find the stack trace as well as a patch that fixes the problem. |
| Comments |
| Comment by Chris Miner [ 14/Sep/06 ] |
|
Okay this is the real patch. The other can be deleted. |
| Comment by Chris Miner [ 14/Sep/06 ] |
|
And this is the real stack trace. Delete the other one. |
| Comment by Philipp Bracher [ 15/Sep/06 ] |
|
commited |