Re: asp.net postbacks don't work after leaving browser open all night w/ windows integrated authentication
- From: Ken Yee <kenkyee@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 25 Oct 2006 08:38:28 -0700
"Scott M." <s-mar@xxxxxxxxxxxxx> wrote in
news:uI6L0CV9GHA.4552@xxxxxxxxxxxxxxxxxxxx:
I don't know, it seems like it is a server-side authentication issue
to me. Client-side pages are static, if they do something at 7pm, they
do it again at 7am. If that is not happening for you, it is most
likely a server-side problem.
With basic authentication, I suspect this is true since the browser will
send over the username/password automatically if the server says it is
not authenticated.
My suspicion of what happens with windows authentication as follows:
- MSIE client issues username/password to server
- server issues a windows integrated authentication token w/ some
expiration date
- client uses token for a while
- the next morning, the token has already expired, but the client is
still using the same token (the stale cache issue), so the old cached
pages work but the non-cached ones do not
I was hoping someone else may have experienced the same issue...
ken
.
- References:
- Prev by Date: Re: ActiveDirectoryMembershipProvider.ValidateUser problem
- Next by Date: Re: ActiveDirectoryMembershipProvider.ValidateUser problem
- Previous by thread: Re: asp.net postbacks don't work after leaving browser open all night w/ windows integrated authentication
- Next by thread: Re: Roles.IsUserInRole != Context.User.IsInRole
- Index(es):