Hello,
I am battling a long term problem regarding integrated authentication and
impersonation. I have an intranet that uses only integrated authentication to
validate my users. The web site is built in asp.net 2.0 and is running under
IIS6 with impersonation enabled. The web site interacts with a SQL 2000
database running on a separate member server. Authentication works fine
between my clients and the website, but I am running into problems with pages
that need to access the database. Problem is, when a user navigates to a page
that queries the database, things run fine at first and all the pages open.
After 10 minutes or so of idle time, however, the users begin seeing the
dreaded "Login failed for user '(null)'" error when trying to access a
database related page. All other pages that require integrated authentication
on the site are still accessible - it is only the database credentials that
are getting somehow dropped. I have researched this issue again and again,
and I have not been able to find a rational explanation as to why the DB
connection works at first and times out after idle periods. The only way for
my users to regain access to the DB related pages is for them to close their
browser and wait a few minutes before trying again.
Most of the articles I have read indicate that I need to use delegation in
this type of setup. I have not set up delegation, however. I figure if it
works at first, then I shouldn't need delegation in my environment. Anybody
have any suggestions or ideas?
Thanks,
JS
