I’m trying to get a login prompt to come up without have to put ?Open&Login.
For example, I have a document in a database which has anonymous as reader in the ACL. I have put a readers field in the document where anonymous is not part of. So when I put the URL in the browser, I get the error
"HTTP Web Server: Lotus Notes Exception - Entry not found in index "
which I understand since the document doesn’t appear for Anonymous.
However, if I put the same URL with ?Open&Login, I get the login prompt which once the login info is entered, it works fine. How do I get this prompt to come up without adding &login on pages that need authentication.
I have tried using $PublicAccess but that didn’t work either as it gave me the same problem.
The problem, as I understand it, is that the URL refers to two object: the view, and the document. But the Domino server only checks to see if it authenticates you once: when you are accessing the first object, the view. Since your view is accessible to anonymous, the server decides it doesn’t need to authenticate you.
The only way I know around this is to access the documents through a view that has its own readers list attached to it, referencing a role that is assigned to a group or wildcard that resolves to your list of authenticated users.
A document can appear in as many views as you need it to be in. So, my suggestion is that you display whatever views you need to, but that you construct your URLs (in views, on pages, in docs, whatever) so that they specify a view that has access protection.
I have a several documents that have links to other documents that are all located in the same view. However, some of those documents are for members only and others are for anonymous.
What I want is that when anonymous views that document and clicks on a link that is for members only, a login prompt should appear and not a “Entry not found in index” error. Basically, I don’t care if anonymous knows those documents exist, as long as he is being prompted for a login. Notes hides the document and makes it look like it doesn’t exist.
Problem with putting them in a separate view that is restricted is that the links will have to be coded differently by the client. They are already finding it difficult to put a simple anchor link, asking them to keep track of locked and unlocked documents by calling a different view would be too complicated for them.