Description
hierarchical based facet rules used to not be possible to rewrite to a correct authorization query (resulting in wrong total counts, never in unauthorized access though!!). With the introduction of jcr:path based hierarchical facet rules, excluding now also all nodes below 'myfolder' in the facet rule example below is trivial.
<?xml version="1.0" encoding="UTF-8"?> <sv:node xmlns:sv="http://www.jcp.org/jcr/sv/1.0" sv:name="hide-resourcebundles-folder"> <sv:property sv:name="jcr:primaryType" sv:type="Name"> <sv:value>hipposys:facetrule</sv:value> </sv:property> <sv:property sv:name="hipposys:equals" sv:type="Boolean"> <sv:value>false</sv:value> </sv:property> <sv:property sv:name="hipposys:facet" sv:type="String"> <sv:value>jcr:uuid</sv:value> </sv:property> <sv:property sv:name="hipposys:filter" sv:type="Boolean"> <sv:value>false</sv:value> </sv:property> <sv:property sv:name="hipposys:type" sv:type="String"> <sv:value>Reference</sv:value> </sv:property> <sv:property sv:name="hipposys:value" sv:type="String"> <sv:value>/content/documents/myfolder</sv:value> </sv:property> </sv:node>
Attachments
Issue Links
- relates to
-
REPO-1337 Authorization query does not exclude all descendant nodes of node with id 'xyz' when there is a facet rule that says 'jcr:uuid != xyz'
-
- Closed
-