Re: Integrated Windows Authentication Timeout?

Yes thank you very much for the info about the 30 minute behavior in IE. I
think that is definitely related. But I do believe that we have both the
FQDN and the NetBios set up with SPNs. One thing we cannot figure out is how
to list them since they are associated to a domain account.

setspn -L <COMPUTER NAME>

will list them for the default account of the computer but doesn't seem to
show those for the domain account.

Anyone know how to list them for the domain account?


"Joe Kaplan" wrote:

That's interesting info. Thanks Henning!

I think the behavior IE is showing is a bit bizarre, but it is good to know
it exists. It sounds like the key thing is to make sure the SPN is
registered for the NetBIOS name as well so it can do Kerb.

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
--
"Henning Krause [MVP - Exchange]" <newsgroups_remove@xxxxxxxxxxxxxxxxx>
wrote in message news:eLklU2sdHHA.4696@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

the Internet Explorer reverts from the domain name to the netbios name for
some reason after 30 minutes. It's explained here:
http://support.microsoft.com/kb/871179

This might help.

Best regards,
Henning Krause

"Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ew67WVkdHHA.3632@xxxxxxxxxxxxxxxxxxxxxxx
That's pretty weird. Are you auditing logon success events on the web
server? Do you see anything different for the NTLM requests? Is it
possible that a different host name is being used (such as the IP address
or something else) for one of the subsequent requests that would break
Kerberos auth?

You might consider enabling protocol transition authentication since you
are using constrained delegation anyway. Then this wouldn't be a
problem. However, it would still be good and useful to fix it.

If you have "Negotiate" authentication set in the metabase (the default),
then this can still negotiate down to NTLM if for some reason the
protocol thinks that Kerberos is unavailable. This is the aspect of
Negotiate auth that makes it so functional for older clients that need
NTLM and so frustrating for app developers that really need Kerberos
auth. :)

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:D442C7C0-35FE-40A6-8897-C10A7004C306@xxxxxxxxxxxxxxxx
Okay, so I have narrowed the problem down to Kerberos Authentication.
When a
user first visits the site all authenticiation is done via Kerberos.
After
the period of inactiity, the next hit to the web site authenticates
using
NTLM for some reason. Since we have Constrained Delegation set up as
"Kerberos Only" it does not forward the NTLM credentials to the database
server. This results in the "NT AUTHORITY\Anonymous logon" error.

So the question is why does it fall back to NTLM after a period of
inactivity of about 30 minutes? I have used kerbtray.exe to look at the
tickets and they all say 10 hours until expiration with 7 days of
renewal.

Should I edit the Metabase on the web server to not allow NTLM? Would
that
force the authentication to Kerberos or would the authentication just
fail?

Thanks,

Bradley

"anonymous" wrote:

I found this, do you think it could be related:

http://technet2.microsoft.com/WindowsServer/en/library/b36b8071-3cc5-46fa-be13-280aa43f2fd21033.mspx?mfr=true


S4UTicketLifetime
Registry path
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
Version
Windows Server 2003
This entry controls the lifetime, in minutes, of tickets obtained by
S4U
proxy requests. This entry does not exist in the registry by default.
The
default value is 15 minutes.



"anonymous" wrote:

Okay, I got rid of the viewstate error. But I still get the
authentication
error after 20 minutes of inactivity. I have tried disabling the
"shutdown
idle worker processes", and "recycle worker processes" options on the
application pool with no change in this behavior.

Does anyone have any ideas of what could be going wrong? Or
suggestions of
specific things for me to audit or log that might point me in the
right
direction?

"Joe Kaplan" wrote:

No I don't. That's an interesting observation and I don't know if
that is
coincidence or not. The first thing to do would be to figure out
how the
viewstate got corrupted, but I'm not really much of a viewstate
expert, so
I'm not really sure what the best bet is for troubleshooting that
problem.
Someone else will certainly know 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
--
"anonymous" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2B0B127F-D89B-4702-9450-A7D08F5A5908@xxxxxxxxxxxxxxxx
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















.

Relevant Pages

  • Re: using xp credentials for ldap authentication
    ... Windows Negotiate protocol which selects between Kerberos and NTLM. ... Windows Authentication in IIS) and is supported by IE and FireFox to some ... Joe Kaplan-MS MVP Directory Services Programming ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.windows.server.security)
  • Re: Disable Kerberos in a Windows Server 2003 Environment
    ... Kerberos experts who hang out on the activedir.org mailing list that can ... Joe Kaplan-MS MVP Directory Services Programming ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ... authentication to a given service by making sure the service principal ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to bypass Forms Authentication on selected pages programma
    ... Joe Kaplan-MS MVP Directory Services Programming ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ... runs after authentication but before authorization) check the Url ...
    (microsoft.public.dotnet.security)
  • Re: using xp credentials for ldap authentication
    ... Joe Kaplan-MS MVP Directory Services Programming ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ... password into this method and have the server use that data to ... You return the authentication ...
    (microsoft.public.windows.server.security)
  • Re: Integrated Windows Authentication Timeout?
    ... Joe Kaplan-MS MVP Directory Services Programming ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ... If you have "Negotiate" authentication set in the metabase, ... protocol thinks that Kerberos is unavailable. ...
    (microsoft.public.dotnet.framework.aspnet.security)