Hello,

Platform:
Windows Server 2003
IIS 6.0

I have several subsites in a single web site. Is it possible to have
one subsite to use custom login utilizing the CustomAuth.dll (provided
in e.g. IIS 6.0 resource kit) while preserving the integrated windows
authentication in the other subsites? Hierarchically the subsites are
on the same level and they are not nested. To me it seems like the
customauth.dll should be installed as an ISAPI filter and thus it will
affect all the subsites. Is this correct? I played around a little
hoping that it would work individually for each application (like
subsites) and installed the customauth.dll as wildcard mapping and
allowed it in web service extensions, allowed only anonymous access to
the directory and finally removed anonymous read rights from a test
file, but it seemed that then accessing that test file any of the
authentication methods were not working (I just got 401.2 response
without any authentication firing).

[ Post a follow-up to this message ]

Should work. CustomAuth will only work if the request is originally
anonymous, and it explicitly does nothing if other authentication types are
involved. That's what the source code in the freely downloadable Platform
SDK says.

401.2 is not something that CustomAuth will cause, so I think you have some
other configuration issue. 401.2 happens when your browser does not use an
authentication scheme that the server demands.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Dean Kuntz" <mulleteer@ziplip.com> wrote in message
news:de92be2a.0504250723.40020ccc@posting.google.com...
Hello,

Platform:
Windows Server 2003
IIS 6.0

I have several subsites in a single web site. Is it possible to have
one subsite to use custom login utilizing the CustomAuth.dll (provided
in e.g. IIS 6.0 resource kit) while preserving the integrated windows
authentication in the other subsites? Hierarchically the subsites are
on the same level and they are not nested. To me it seems like the
customauth.dll should be installed as an ISAPI filter and thus it will
affect all the subsites. Is this correct? I played around a little
hoping that it would work individually for each application (like
subsites) and installed the customauth.dll as wildcard mapping and
allowed it in web service extensions, allowed only anonymous access to
the directory and finally removed anonymous read rights from a test
file, but it seemed that then accessing that test file any of the
authentication methods were not working (I just got 401.2 response
without any authentication firing).

[ Post a follow-up to this message ]