12-22-04 10:54 PM
Having my own authentication check would involve other security issues. I
think I'd take advantage of the built IIS one.
I now have an idea in my mind. When an authentication fails, the HTTP 401
error triggers a script, which queries the security event log with a WMI
object, and identifies the failure reason with the EventCode, for an
example, 531 for disabled account.
I haven't figured out how the vbscript codewould look like. The first
problem I encountered here is mapping the HTTP 401 error to an URL. What
Bernard replied on my posting on Dec.17 seems to be right. I just can't do
the URL mapping. Annoying...
Ally
"Bernard" <qbernard@hotmail.com.discuss> wrote in message
news:eFIePy95EHA.3736@TK2MSFTNGP10.phx.gbl...
> Unless you are doing your own authentication check, and OS replied you
with
> the correct status. AFAIK, you can't achieve this with built IIS
> authentication and log file status code.
>
> --
> Regards,
> Bernard Cheah
> http://www.tryiis.com/
> http://support.microsoft.com/
> http://www.msmvps.com/bernard/
>
>
>
> "Scilabop" <scilabop@Xuvic.ca> wrote in message
> news:eY8KD165EHA.1408@TK2MSFTNGP10.phx.gbl...
read[vbcol=seagreen]
Hope[vbcol=seagreen]
>
>
[ Post a follow-up to this message ]
|