更新时间:2023-12-01 09:39:28
这是我处理的基础上的这个信息的:
This is the way I've handled a similar situation based on this info:
什么基本情况是,当一个unauthenicated用户点击该网站,他们重定向到WinLogin.aspx。因为匿名是关闭的,集成的安全,使一张支票。如果通过,您的自定义code在WinLogin可以运行。如果综合安全检查失败,出现401错误。您的自定义401页面重定向到login.aspx的,用户可以登录使用的用户名和密码与SQL提供。
What basically happens is that when an unauthenicated user hits the site, they're redirected to WinLogin.aspx. Since anonymous is turned off, integrated security makes a check. If that passes, your custom code in WinLogin can run. If the integrated security check fails, a 401 error occurs. Your custom 401 page redirects to Login.aspx where the user can log in using their username and password with the SQL provider.