Difference between revisions of "Knowledge:Access manager"
From OpenKM Documentation
(→Difference between "simple" and "recursive") |
|||
| Line 15: | Line 15: | ||
Give this repository structure: | Give this repository structure: | ||
| − | * okm:root | + | * [[File:Folder.png]] okm:root |
| − | ** | + | ** [[File:Folder.png]] level-1a |
| − | *** | + | *** [[File:Folder.png]] level-2a |
| − | **** | + | **** [[File:Folder.png]]level-3a |
***** doc-a | ***** doc-a | ||
***** doc-b | ***** doc-b | ||
***** doc-c | ***** doc-c | ||
| − | **** | + | **** [[File:Folder.png]] level-3b |
| − | ** | + | ** [[File:Folder.png]] level-1b |
| − | ** | + | ** [[File:Folder.png]] level-1c |
Revision as of 10:39, 6 October 2012
By default OpenKM 6 is configured this way:
security.access.manager = simple security.search.evaluation = lucene
Which provides great performance by only evaluating a single node. But if you want to evaluate every parent you can change this behavior with these settings:
security.access.manager = recursive security.search.evaluation = [ am_more | am_window | am_limited ]
This will reduce OpenKM performance (at least in search) but will match customer requirements.
Difference between "simple" and "recursive"
Give this repository structure:
-
okm:root
- level-1a
- level-2a
- level-3a
- doc-a
- doc-b
- doc-c
- level-3b
-
-
- level-1b
- level-1c
-
