Hi All,
I have a issue related to authentication on web. I set Anonymous access on a db to “NoAccess” and user get authentication dialong on web when he tries to open. after authentication User open a form and redirct page to a view in names.nsf here again authentication dialog appear. Why this happening? Does the session break? If i open someother db instead of names.nsf with Anonymous access restricted, it works fine.
Any idea?
Subject: Session authentication Problem
Just thinking out loud here, but your username/password combo should stay cached in your browser session as long as it’s open. When the user gets redirected to the names.nsf does it open a new browser window? I’m thinking that maybe a new window needs a new sign-on.
Subject: RE: Session authentication Problem
The new window shouldn’t matter. If the user can’t log in at the new log in screen then there’s some other ACL issue at work. If they can log in, then it sounds like is that you are hitting a different hostname in the new window.
For example, if a user logs in on http://hostname1.yourdomain.com/db.nsf and authenticates there, the authentication cookie is stored on the browser for the remainder of that session. The cookie is bound to that hostname.
If the user is redirected to http://hostname2.yourdomain.com/db.nsf they will need to authenticate again, even if it is the same physical server and database as before.
Subject: RE: Session authentication Problem
Thanks Erik,
You are right in this context but I hardcoded the server path in my application. During testing on various possibilities I figured out that If my db resides at the same level as names.nsf then I don’t get any extra authentication dialog but if my db is in a subfolder under data directory then it ask me for authentication when i try to open names.nsf view. need your opinion.