I have a web app which requires all users to log in and authenticate with Domino. This works well.
The app contains many documents, which are secured using readers fields. This ensures that no-one sees things they shouldn’t see.
However, I am aware that using readers fields puts added load on the server and so I am wondering if there are alternative security methods which are as effective and controllable as readers fields, without the added server load.
Thanks
Subject: Web Security - Options Other Than Reader Fields
There is probably no other way to hide data in a secure way. But you can try other insecure methods which in most cases work good if implemeted correctly.
Use embedded categorized view with “Show single category” parameter and use person’s name for categories.
Use hide-when @Formula to hide paragraphs on forms and show only to the persons listed in a certain field (or have certain role).
Use LotusScript to create web pages and keep documents in another database.
However most examples above should still be combined with readers fields for additional security.
I wouldn’t bother to replace Readers fields to something else if there wasn’t a proved case that they cause a significant performance problem.
/Andrei