We applied the new .net security patch to our development machine. It may be
entirely coincidental, but now authentication hangs.

We use forms authentication and .Net appears to do what it is supposed to do
by passing control to the log in form. We can navigate off the form to other,
non-secured forms. But when we enter user name and password (and the code
behind hits SQL) nothing happens; not even error codes. We're not configured
for debug at this time. So we're having a little trouble pinning the problem
down.

Behavior is the same, even after removing the patch. Has anyone encoutered
this before? thanks.

Exactly which patch was this?


Is the "SQL" that's being hit SQL Server?  If so, have you tried running SQL
Profiler to see if any requests against the db are being issued and, if so,
if the problem might be there?  If you don't actually see activity against
the db, are you sure the web page request is actually hitting the server (as
your IIS logs might show)?  Have you tried monitoring the ASP.NET trace for
the login page?


Show quoteHide quote

ASP.NET form-based authentication help
StreamWriter causes SecurityException when attempting to write to network drive..need help
Sandboxing AppDomain
windows forms UserControl compiled with beta 2 doesn't work with IE
VS2005 - X509 key not loaded correctly for FTPS server authentication ?
Enabling Forms Authentication Stops Button Click Events
Does preJIT protect the assemblies?
Best Practice for ASP.NET access to SQL Server
Communicating between ASP.NET and SQL Server on separate servers
Forms Authentication - how to proceed when valid login?