Hello,
we have a problem with our Domain Indexer (Server R5 english Release 5.07a on AS/400). In some of our applications our developers have included a feature that allows users to define individually who should have access to their documents. They have created the fields 'can always read'(Reader) and 'can always write' (Author).
Let's assume Reader Miller creates a new document with no special security restrictions --> Reader field remains blank and Author field contains Miller and per default a Server group. --> Everyone who has at least Reader Access in the ACL of the database can access this document, and the Domain Indexer picks it up correctly.
Now Reader Miller decides to restrict the reader access for his document to User Smith --> Reader field contains Smith, Author field contains Miller and the Server group. Now Smith and Miller can still access the document, but the domain indexer ignores it, as the Server group is not explicitly listed in the Reader field, but only in the Author field.
I think that this behaviour is inconsistent to the general Notes philosophy: author automatically includes the right to read --> why does the Domain Indexer skip these documents? Does anyone have a similar problem? - I don't think that including the server group into the Reader field by default can be an acceptable solution - or is this another case for the famous quote from Lotus: 'Works as designed'
we have a problem with our Domain Indexer (Server R5 english Release 5.07a on AS/400). In some of our applications our developers have included a feature that allows users to define individually who should have access to their documents. They have created the fields 'can always read'(Reader) and 'can always write' (Author).
Let's assume Reader Miller creates a new document with no special security restrictions --> Reader field remains blank and Author field contains Miller and per default a Server group. --> Everyone who has at least Reader Access in the ACL of the database can access this document, and the Domain Indexer picks it up correctly.
Now Reader Miller decides to restrict the reader access for his document to User Smith --> Reader field contains Smith, Author field contains Miller and the Server group. Now Smith and Miller can still access the document, but the domain indexer ignores it, as the Server group is not explicitly listed in the Reader field, but only in the Author field.
I think that this behaviour is inconsistent to the general Notes philosophy: author automatically includes the right to read --> why does the Domain Indexer skip these documents? Does anyone have a similar problem? - I don't think that including the server group into the Reader field by default can be an acceptable solution - or is this another case for the famous quote from Lotus: 'Works as designed'