[MAGNOLIA-2975] Restricting access to root in reposiory makes activation of versioned content fail Created: 16/Dec/09  Updated: 23/Jan/13  Resolved: 06/Jan/10

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.2.2
Fix Version/s: 4.3

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace.txt    
Issue Links:
dependency
duplicate
is duplicated by MAGNOLIA-2990 user eric cannot see page versions Closed
is duplicated by MGNLSTK-580 update ACL's for demo user "Peter" to... Closed
relation
is related to MAGNOLIA-1753 activation: latest security fix block... Closed
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

 Description   

When user doesn't have rights to write to the root of DMS, attempt to retrieve version of the content fails with exception (attached)

To reproduce:

  • add version command to the activation command chain
  • make sure workflow is not used
  • restrict access to root by creating ACL:
    • read/write:selected&subnodes:/$
    • read/write:selected&subnodes:/somePage
  • login as a user with the permissions described above and attempt to activate the /somePage

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