Page History

...

• Add a requiredPermissions property under AvailabilityDefinition or AccessDefinition
  
  • comma separated list of JCR permissions (aka action strings)
    
    • add_node, set_property, remove, read
    • we should rather use Magnolia permissions
    •  doesn't fit for upcoming custom permissions
  • naming is debatable (permissions > requiredPermissions)
• Add a writePermissionRequired boolean property under AvailabilityDefinition or AccessDefinition
  
  • simply checks for Magnolia WRITE permission
  •  which entry point? cannot use PermissionUtil
  • for custom permissions, people will need to implement AvailabilityRule
•  We unify availability's access, ruleClass and other criteria using voters, in a future major version
  
  • supports custom permissions (forum), even non-JCR based, using dedicated voters
  •  Do we keep availability's "shorthands"?
    • nodeTypes, root, properties...
    • yet update underlying implementation to work with voters
      
    • Proposal: how about maintaining all the shorthands we have and also providing a rather smooth mechanism of moving from old impl to the new one by implementing a custom Node2BeanTransformerImpl
      that would build voters based on the properties from AvailabilityDefinition (e.g. once the property name is nodes - we generate a corresponding voter)?
•  For 5.2.x, we introduce a delegating AvailabilityRule which helps us already start working with voters
  

  • getting well prepared for migrating to the next approach

...