Why doesn the K2 Server honor security changes on documents after the collection has been built?
Verity stores the Access Control List (ACL) in a field. In the case of the Windows NTFS file-system, this is_VgwNTFileAccessCache. In the case of the UNIX file-system, this is _VgwUnixFileAccessCache. If you want to do real-time lookups you can disable the ACL caching by editing the vgwfsys.prm file. Following is an example using the UNIX file-system: If you index the following document: -rw-r–r– 1 techtest verity 6 Nov 22 10:06 1.txt where “Other” (that is, everyone) has read access, but then after having created the collection, you change the permissions so that “Other” does not have access: -rw-r—– 1 techtest verity 6 Nov 22 10:06 1.
Related Questions
- Are documents related to the establishment and operation of DOEs LSN collection and server considered potentially relevant and should they be included in the LSN itself?
- Why doesn the K2 Server honor security changes on documents after the collection has been built?
- Why does K2 Server fail to load an ODBC collection defined as anonymous by Verity?
