Re: Integrated Windows Authentication Timeout?
- From: anonymous <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 26 Feb 2007 07:24:00 -0800
Seems like this event correlates to the error:
"Viewstate verification failed. Reason: The viewstate supplied failed
integrity check."
Any idea what is going on?
"Joe Kaplan" wrote:
Like I said before, I've never seen this, so I'm not sure what the likely.
culprit is. However, you might want to see if your app pool is recycling
and if there is a correlation there. You should see events in the System
event log indicating a recycle event.
Also, I'd suggest bumping up the auditing on both the web server and SQL
server so that you are auditing both logon success and failure messages.
That way, you should get more diagnostic info in the security event log as
to what is transpiring.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"anonymous" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:34C2A7A8-B2CA-4880-A024-08A1326CBE61@xxxxxxxxxxxxxxxx
Joe,
Thanks for the reply. It does happen on the attempt to connect to the SQL
Server. I have not been able to reproduce it with the same setup on IIS
5.0
if that helps. Can something with the Application Pool be timing out?
"Joe Kaplan" wrote:
Is that exception thrown by the connection attempt to SQL (thus an error
in
the delegation) or does that happen at the browser level? Can you show a
stack trace?
IWA doesn't time out, although Kerberos tickets can expire. 20 minutes
sounds way too short to have anything to do with that though.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"Bradley Landis" <BradleyLandis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:76CA1BCC-67A8-462A-A41D-F3D082DB395F@xxxxxxxxxxxxxxxx
Environment:
IIS 6.0
ASP.NET 2.0
Integrated Windows Authentication
Identity impersonate=true
Constrained Delegation set to impersonate user while connecting to SQL
Server
Problem scenario:
Everything above works perfectly well except when the user leaves a
page
sit
idle for 20 minutes or so. At that point if they come back and click a
link
on the page the following error is thrown:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
I do not use any session data so the session timeout should not be the
problem. I tried extending the session timeout anyway as an experiment
and
it did not have any effect. I know there are other timeouts associated
with
Forms Authentication, but are there other timeouts associated with
Integrated
Windows Authentication? If so, how and where do I configure them.
Thank you,
Bradley
- Follow-Ups:
- Re: Integrated Windows Authentication Timeout?
- From: Joe Kaplan
- Re: Integrated Windows Authentication Timeout?
- Prev by Date: Re: Getting GROUPS from Active Directory by inputing an AD username
- Next by Date: Using Windows Authentication in ASP.NET - Adding properties to users
- Previous by thread: Re: Basic password security question
- Next by thread: Re: Integrated Windows Authentication Timeout?
- Index(es):
Relevant Pages
|