I followed the instructions for installing the CustomAuth.dll as an ISAPI 
filer at 
http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO. 
The server I'm playing with does not have Sharepoint Portal Server 
installed.  I simply want to experiment with CustomAuth.dll as a method of 
authentication for a website.

I downloaded the source code, built the dll, and installed it as an ISAPI 
filter for a website in IIS (Windows 2003 Server with IIS 6.0).  The site 
only allows anonymous access but the CustomAuth.dll has no effect.  I'm not 
getting any errors, but I'm not being redirected to the default login form 
either.  I basically have no indication that it's even attempting to run.

I've tried installing it as a wildcard script map as well with the same 
result.

I've looked around and it seems other people have got it to run no problem. 
What am I doing wrong?

Any help would be very much appreciated.

Thanks,
Dan

You need to install CustomAuth.dll as global ISAPI Filter, and also install 
it as wildcard application mapping at the parent node of the URL namespace 
you want to protect. Since you installed global ISAPI Filter, you need to 
either recycle the Application Pool serving the URL namespace being 
protected, or restart IIS if running in IIS5 Compatibility Mode.

Installing as a wildcard application mapping does not guarantee that it runs 
due to how application mappings work. You need to make sure that the 
applicable mapping is "active" at the URL namespace, either through 
inheritance (default) or explicit setting (if you've customized).

-- 
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"Dan"  wrote in message 
news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>I followed the instructions for installing the CustomAuth.dll as an ISAPI 
>filer at 
>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO. 
>The server I'm playing with does not have Sharepoint Portal Server 
>installed.  I simply want to experiment with CustomAuth.dll as a method of 
>authentication for a website.
>
> I downloaded the source code, built the dll, and installed it as an ISAPI 
> filter for a website in IIS (Windows 2003 Server with IIS 6.0).  The site 
> only allows anonymous access but the CustomAuth.dll has no effect.  I'm 
> not getting any errors, but I'm not being redirected to the default login 
> form either.  I basically have no indication that it's even attempting to 
> run.
>
> I've tried installing it as a wildcard script map as well with the same 
> result.
>
> I've looked around and it seems other people have got it to run no 
> problem. What am I doing wrong?
>
> Any help would be very much appreciated.
>
> Thanks,
> Dan
>

After looking at further, I want to make sure I'm installing the dll 
correctly as a wildcard script map.

IIS->website->properties->Home Directory->Configuration->Add

In the Add dialog I use the browse button to select the CustomAuth.dll

I leave the radio button set to "All Verbs".

I leave the "Script engine" checkbox checked.

I uncheck the "Check that file exists" checkbox.

What do I put in the extension text box?  Since it's suppose to be a 
wildcard script map I had been trying "%".

Is this correct so far?

Thanks,
Dan

"Dan"  wrote in message 
news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>I followed the instructions for installing the CustomAuth.dll as an ISAPI 
>filer at 
>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO. 
>The server I'm playing with does not have Sharepoint Portal Server 
>installed.  I simply want to experiment with CustomAuth.dll as a method of 
>authentication for a website.
>
> I downloaded the source code, built the dll, and installed it as an ISAPI 
> filter for a website in IIS (Windows 2003 Server with IIS 6.0).  The site 
> only allows anonymous access but the CustomAuth.dll has no effect.  I'm 
> not getting any errors, but I'm not being redirected to the default login 
> form either.  I basically have no indication that it's even attempting to 
> run.
>
> I've tried installing it as a wildcard script map as well with the same 
> result.
>
> I've looked around and it seems other people have got it to run no 
> problem. What am I doing wrong?
>
> Any help would be very much appreciated.
>
> Thanks,
> Dan
>

You are not adding a wildcard application mapping. You have been mapping a 
Script Engine to a URL with an extension of %.

Inside the same Configuration tab, where the Application Mappings are on 
top - the Wildcard Application Mappings are on the bottom. You click 
"Insert" to add.

-- 
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"Dan"  wrote in message 
news:%238F6dDWHGHA.1452@TK2MSFTNGP11.phx.gbl...
> After looking at further, I want to make sure I'm installing the dll 
> correctly as a wildcard script map.
>
> IIS->website->properties->Home Directory->Configuration->Add
>
> In the Add dialog I use the browse button to select the CustomAuth.dll
>
> I leave the radio button set to "All Verbs".
>
> I leave the "Script engine" checkbox checked.
>
> I uncheck the "Check that file exists" checkbox.
>
> What do I put in the extension text box?  Since it's suppose to be a 
> wildcard script map I had been trying "%".
>
> Is this correct so far?
>
> Thanks,
> Dan
>
> "Dan"  wrote in message 
> news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>>I followed the instructions for installing the CustomAuth.dll as an ISAPI 
>>filer at 
>>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO. 
>>The server I'm playing with does not have Sharepoint Portal Server 
>>installed.  I simply want to experiment with CustomAuth.dll as a method of 
>>authentication for a website.
>>
>> I downloaded the source code, built the dll, and installed it as an ISAPI 
>> filter for a website in IIS (Windows 2003 Server with IIS 6.0).  The site 
>> only allows anonymous access but the CustomAuth.dll has no effect.  I'm 
>> not getting any errors, but I'm not being redirected to the default login 
>> form either.  I basically have no indication that it's even attempting to 
>> run.
>>
>> I've tried installing it as a wildcard script map as well with the same 
>> result.
>>
>> I've looked around and it seems other people have got it to run no 
>> problem. What am I doing wrong?
>>
>> Any help would be very much appreciated.
>>
>> Thanks,
>> Dan
>>
>
>

Oops, that was embarassing.

Thanks for the help.


"David Wang [Msft]"  wrote in message 
news:ODYc7QWHGHA.3728@tk2msftngp13.phx.gbl...
> You are not adding a wildcard application mapping. You have been mapping a 
> Script Engine to a URL with an extension of %.
>
> Inside the same Configuration tab, where the Application Mappings are on 
> top - the Wildcard Application Mappings are on the bottom. You click 
> "Insert" to add.
>
> -- 
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
> //
>
> "Dan"  wrote in message 
> news:%238F6dDWHGHA.1452@TK2MSFTNGP11.phx.gbl...
>> After looking at further, I want to make sure I'm installing the dll 
>> correctly as a wildcard script map.
>>
>> IIS->website->properties->Home Directory->Configuration->Add
>>
>> In the Add dialog I use the browse button to select the CustomAuth.dll
>>
>> I leave the radio button set to "All Verbs".
>>
>> I leave the "Script engine" checkbox checked.
>>
>> I uncheck the "Check that file exists" checkbox.
>>
>> What do I put in the extension text box?  Since it's suppose to be a 
>> wildcard script map I had been trying "%".
>>
>> Is this correct so far?
>>
>> Thanks,
>> Dan
>>
>> "Dan"  wrote in message 
>> news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>>>I followed the instructions for installing the CustomAuth.dll as an ISAPI 
>>>filer at 
>>>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO. 
>>>The server I'm playing with does not have Sharepoint Portal Server 
>>>installed.  I simply want to experiment with CustomAuth.dll as a method 
>>>of authentication for a website.
>>>
>>> I downloaded the source code, built the dll, and installed it as an 
>>> ISAPI filter for a website in IIS (Windows 2003 Server with IIS 6.0). 
>>> The site only allows anonymous access but the CustomAuth.dll has no 
>>> effect.  I'm not getting any errors, but I'm not being redirected to the 
>>> default login form either.  I basically have no indication that it's 
>>> even attempting to run.
>>>
>>> I've tried installing it as a wildcard script map as well with the same 
>>> result.
>>>
>>> I've looked around and it seems other people have got it to run no 
>>> problem. What am I doing wrong?
>>>
>>> Any help would be very much appreciated.
>>>
>>> Thanks,
>>> Dan
>>>
>>
>>
>
>

Ok, now that I have definitely installed it as an ISAPI Filter and a 
Wildcard Script map, I still have no indication that it is attempting to 
run.

I've tried restarting IIS, and rebooting the server, nothing.  I don't get 
any errors but I'm not prompted either, and the Event Log doesn't report 
anything.

The only websites on the server are "Default Web Site", and "Microsoft 
SharePoint Administration" (not sure why that's there as Sharepoint isn't 
installed but anyway...).

"Default Web Site" has one virtual directory named "Test".

I installed CustomAuth as an ISAPI filter and Wildcard Script Map on 
"Default Web Site".  And the "Test" virtual directory inherited the Wildcard 
Script Map.  The Default Web Site already had an ISAPI filter named 
"fpexedll.dll", I believe that's for FrontPage Server Extensions.

Any ideas?

Thanks,
Dan

"David Wang [Msft]"  wrote in message 
news:%23Wd2d$VHGHA.3000@TK2MSFTNGP14.phx.gbl...
> You need to install CustomAuth.dll as global ISAPI Filter, and also 
> install it as wildcard application mapping at the parent node of the URL 
> namespace you want to protect. Since you installed global ISAPI Filter, 
> you need to either recycle the Application Pool serving the URL namespace 
> being protected, or restart IIS if running in IIS5 Compatibility Mode.
>
> Installing as a wildcard application mapping does not guarantee that it 
> runs due to how application mappings work. You need to make sure that the 
> applicable mapping is "active" at the URL namespace, either through 
> inheritance (default) or explicit setting (if you've customized).
>
> -- 
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
> //
>
> "Dan"  wrote in message 
> news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>>I followed the instructions for installing the CustomAuth.dll as an ISAPI 
>>filer at 
>>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO. 
>>The server I'm playing with does not have Sharepoint Portal Server 
>>installed.  I simply want to experiment with CustomAuth.dll as a method of 
>>authentication for a website.
>>
>> I downloaded the source code, built the dll, and installed it as an ISAPI 
>> filter for a website in IIS (Windows 2003 Server with IIS 6.0).  The site 
>> only allows anonymous access but the CustomAuth.dll has no effect.  I'm 
>> not getting any errors, but I'm not being redirected to the default login 
>> form either.  I basically have no indication that it's even attempting to 
>> run.
>>
>> I've tried installing it as a wildcard script map as well with the same 
>> result.
>>
>> I've looked around and it seems other people have got it to run no 
>> problem. What am I doing wrong?
>>
>> Any help would be very much appreciated.
>>
>> Thanks,
>> Dan
>>
>
>

Ok, now that I have definitely installed it as an ISAPI Filter and a 
Wildcard Script map, I still have no indication that it is attempting to 
run.

I've tried restarting IIS, and rebooting the server, nothing.  I don't get 
any errors but I'm not prompted either, and the Event Log doesn't report 
anything.

The only websites on the server are "Default Web Site", and "Microsoft 
SharePoint Administration" (not sure why that's there as Sharepoint isn't 
installed but anyway...).

"Default Web Site" has one virtual directory named "Test".

I installed CustomAuth as an ISAPI filter and Wildcard Script Map on 
"Default Web Site".  And the "Test" virtual directory inherited the Wildcard 
Script Map.  The Default Web Site already had an ISAPI filter named 
"fpexedll.dll", I believe that's for FrontPage Server Extensions.

Any ideas?

Thanks,
Dan


"Dan" wrote:

> Oops, that was embarassing.
> 
> Thanks for the help.
> 
> 
> "David Wang [Msft]"  wrote in message 
> news:ODYc7QWHGHA.3728@tk2msftngp13.phx.gbl...
> > You are not adding a wildcard application mapping. You have been mapping a 
> > Script Engine to a URL with an extension of %.
> >
> > Inside the same Configuration tab, where the Application Mappings are on 
> > top - the Wildcard Application Mappings are on the bottom. You click 
> > "Insert" to add.
> >
> > -- 
> > //David
> > IIS
> > http://blogs.msdn.com/David.Wang
> > This posting is provided "AS IS" with no warranties, and confers no 
> > rights.
> > //
> >
> > "Dan"  wrote in message 
> > news:%238F6dDWHGHA.1452@TK2MSFTNGP11.phx.gbl...
> >> After looking at further, I want to make sure I'm installing the dll 
> >> correctly as a wildcard script map.
> >>
> >> IIS->website->properties->Home Directory->Configuration->Add
> >>
> >> In the Add dialog I use the browse button to select the CustomAuth.dll
> >>
> >> I leave the radio button set to "All Verbs".
> >>
> >> I leave the "Script engine" checkbox checked.
> >>
> >> I uncheck the "Check that file exists" checkbox.
> >>
> >> What do I put in the extension text box?  Since it's suppose to be a 
> >> wildcard script map I had been trying "%".
> >>
> >> Is this correct so far?
> >>
> >> Thanks,
> >> Dan
> >>
> >> "Dan"  wrote in message 
> >> news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
> >>>I followed the instructions for installing the CustomAuth.dll as an ISAPI 
> >>>filer at 
> >>>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO. 
> >>>The server I'm playing with does not have Sharepoint Portal Server 
> >>>installed.  I simply want to experiment with CustomAuth.dll as a method 
> >>>of authentication for a website.
> >>>
> >>> I downloaded the source code, built the dll, and installed it as an 
> >>> ISAPI filter for a website in IIS (Windows 2003 Server with IIS 6.0). 
> >>> The site only allows anonymous access but the CustomAuth.dll has no 
> >>> effect.  I'm not getting any errors, but I'm not being redirected to the 
> >>> default login form either.  I basically have no indication that it's 
> >>> even attempting to run.
> >>>
> >>> I've tried installing it as a wildcard script map as well with the same 
> >>> result.
> >>>
> >>> I've looked around and it seems other people have got it to run no 
> >>> problem. What am I doing wrong?
> >>>
> >>> Any help would be very much appreciated.
> >>>
> >>> Thanks,
> >>> Dan
> >>>
> >>
> >>
> >
> > 
> 
> 
>

Perhaps silly but have you checked the Web Service Extensions section to see 
if ISAPI Extensions are allowed or not ? I dont know if registering it 
qualifies as makeing it "known".



"Dan"  wrote in message 
news:1CEADFFC-13E6-4CE4-B068-096DFB2EC3C8@microsoft.com...
> Ok, now that I have definitely installed it as an ISAPI Filter and a
> Wildcard Script map, I still have no indication that it is attempting to
> run.
>
> I've tried restarting IIS, and rebooting the server, nothing.  I don't get
> any errors but I'm not prompted either, and the Event Log doesn't report
> anything.
>
> The only websites on the server are "Default Web Site", and "Microsoft
> SharePoint Administration" (not sure why that's there as Sharepoint isn't
> installed but anyway...).
>
> "Default Web Site" has one virtual directory named "Test".
>
> I installed CustomAuth as an ISAPI filter and Wildcard Script Map on
> "Default Web Site".  And the "Test" virtual directory inherited the 
> Wildcard
> Script Map.  The Default Web Site already had an ISAPI filter named
> "fpexedll.dll", I believe that's for FrontPage Server Extensions.
>
> Any ideas?
>
> Thanks,
> Dan
>
>
> "Dan" wrote:
>
>> Oops, that was embarassing.
>>
>> Thanks for the help.
>>
>>
>> "David Wang [Msft]"  wrote in message
>> news:ODYc7QWHGHA.3728@tk2msftngp13.phx.gbl...
>> > You are not adding a wildcard application mapping. You have been 
>> > mapping a
>> > Script Engine to a URL with an extension of %.
>> >
>> > Inside the same Configuration tab, where the Application Mappings are 
>> > on
>> > top - the Wildcard Application Mappings are on the bottom. You click
>> > "Insert" to add.
>> >
>> > -- 
>> > //David
>> > IIS
>> > http://blogs.msdn.com/David.Wang
>> > This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> > //
>> >
>> > "Dan"  wrote in message
>> > news:%238F6dDWHGHA.1452@TK2MSFTNGP11.phx.gbl...
>> >> After looking at further, I want to make sure I'm installing the dll
>> >> correctly as a wildcard script map.
>> >>
>> >> IIS->website->properties->Home Directory->Configuration->Add
>> >>
>> >> In the Add dialog I use the browse button to select the CustomAuth.dll
>> >>
>> >> I leave the radio button set to "All Verbs".
>> >>
>> >> I leave the "Script engine" checkbox checked.
>> >>
>> >> I uncheck the "Check that file exists" checkbox.
>> >>
>> >> What do I put in the extension text box?  Since it's suppose to be a
>> >> wildcard script map I had been trying "%".
>> >>
>> >> Is this correct so far?
>> >>
>> >> Thanks,
>> >> Dan
>> >>
>> >> "Dan"  wrote in message
>> >> news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>> >>>I followed the instructions for installing the CustomAuth.dll as an 
>> >>>ISAPI
>> >>>filer at
>> >>>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO.
>> >>>The server I'm playing with does not have Sharepoint Portal Server
>> >>>installed.  I simply want to experiment with CustomAuth.dll as a 
>> >>>method
>> >>>of authentication for a website.
>> >>>
>> >>> I downloaded the source code, built the dll, and installed it as an
>> >>> ISAPI filter for a website in IIS (Windows 2003 Server with IIS 6.0).
>> >>> The site only allows anonymous access but the CustomAuth.dll has no
>> >>> effect.  I'm not getting any errors, but I'm not being redirected to 
>> >>> the
>> >>> default login form either.  I basically have no indication that it's
>> >>> even attempting to run.
>> >>>
>> >>> I've tried installing it as a wildcard script map as well with the 
>> >>> same
>> >>> result.
>> >>>
>> >>> I've looked around and it seems other people have got it to run no
>> >>> problem. What am I doing wrong?
>> >>>
>> >>> Any help would be very much appreciated.
>> >>>
>> >>> Thanks,
>> >>> Dan
>> >>>
>> >>
>> >>
>> >
>> >
>>
>>
>>

I have and it is set to be allowed in the Web Service Extensions folder but 
I don't have any indication that it is attempting to run.

Any ideas?

Thanks,
Dan

"Robert Ginsburg"  wrote in message 
news:OzldIloHGHA.3944@tk2msftngp13.phx.gbl...
> Perhaps silly but have you checked the Web Service Extensions section to 
> see if ISAPI Extensions are allowed or not ? I dont know if registering it 
> qualifies as makeing it "known".
>
>
>
> "Dan"  wrote in message 
> news:1CEADFFC-13E6-4CE4-B068-096DFB2EC3C8@microsoft.com...
>> Ok, now that I have definitely installed it as an ISAPI Filter and a
>> Wildcard Script map, I still have no indication that it is attempting to
>> run.
>>
>> I've tried restarting IIS, and rebooting the server, nothing.  I don't 
>> get
>> any errors but I'm not prompted either, and the Event Log doesn't report
>> anything.
>>
>> The only websites on the server are "Default Web Site", and "Microsoft
>> SharePoint Administration" (not sure why that's there as Sharepoint isn't
>> installed but anyway...).
>>
>> "Default Web Site" has one virtual directory named "Test".
>>
>> I installed CustomAuth as an ISAPI filter and Wildcard Script Map on
>> "Default Web Site".  And the "Test" virtual directory inherited the 
>> Wildcard
>> Script Map.  The Default Web Site already had an ISAPI filter named
>> "fpexedll.dll", I believe that's for FrontPage Server Extensions.
>>
>> Any ideas?
>>
>> Thanks,
>> Dan
>>
>>
>> "Dan" wrote:
>>
>>> Oops, that was embarassing.
>>>
>>> Thanks for the help.
>>>
>>>
>>> "David Wang [Msft]"  wrote in message
>>> news:ODYc7QWHGHA.3728@tk2msftngp13.phx.gbl...
>>> > You are not adding a wildcard application mapping. You have been 
>>> > mapping a
>>> > Script Engine to a URL with an extension of %.
>>> >
>>> > Inside the same Configuration tab, where the Application Mappings are 
>>> > on
>>> > top - the Wildcard Application Mappings are on the bottom. You click
>>> > "Insert" to add.
>>> >
>>> > -- 
>>> > //David
>>> > IIS
>>> > http://blogs.msdn.com/David.Wang
>>> > This posting is provided "AS IS" with no warranties, and confers no
>>> > rights.
>>> > //
>>> >
>>> > "Dan"  wrote in message
>>> > news:%238F6dDWHGHA.1452@TK2MSFTNGP11.phx.gbl...
>>> >> After looking at further, I want to make sure I'm installing the dll
>>> >> correctly as a wildcard script map.
>>> >>
>>> >> IIS->website->properties->Home Directory->Configuration->Add
>>> >>
>>> >> In the Add dialog I use the browse button to select the 
>>> >> CustomAuth.dll
>>> >>
>>> >> I leave the radio button set to "All Verbs".
>>> >>
>>> >> I leave the "Script engine" checkbox checked.
>>> >>
>>> >> I uncheck the "Check that file exists" checkbox.
>>> >>
>>> >> What do I put in the extension text box?  Since it's suppose to be a
>>> >> wildcard script map I had been trying "%".
>>> >>
>>> >> Is this correct so far?
>>> >>
>>> >> Thanks,
>>> >> Dan
>>> >>
>>> >> "Dan"  wrote in message
>>> >> news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>>> >>>I followed the instructions for installing the CustomAuth.dll as an 
>>> >>>ISAPI
>>> >>>filer at
>>> >>>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO.
>>> >>>The server I'm playing with does not have Sharepoint Portal Server
>>> >>>installed.  I simply want to experiment with CustomAuth.dll as a 
>>> >>>method
>>> >>>of authentication for a website.
>>> >>>
>>> >>> I downloaded the source code, built the dll, and installed it as an
>>> >>> ISAPI filter for a website in IIS (Windows 2003 Server with IIS 
>>> >>> 6.0).
>>> >>> The site only allows anonymous access but the CustomAuth.dll has no
>>> >>> effect.  I'm not getting any errors, but I'm not being redirected to 
>>> >>> the
>>> >>> default login form either.  I basically have no indication that it's
>>> >>> even attempting to run.
>>> >>>
>>> >>> I've tried installing it as a wildcard script map as well with the 
>>> >>> same
>>> >>> result.
>>> >>>
>>> >>> I've looked around and it seems other people have got it to run no
>>> >>> problem. What am I doing wrong?
>>> >>>
>>> >>> Any help would be very much appreciated.
>>> >>>
>>> >>> Thanks,
>>> >>> Dan
>>> >>>
>>> >>
>>> >>
>>> >
>>> >
>>>
>>>
>>>
>
>

Sharepoint website and fpexedll.dll exists because Windows Sharepoint is 
installed.

Did you also make sure that ONLY anonymous authentication is enabled 
everywhere that you want CustomAuth to be active (and have CustomAuth.dll 
active as a wildcard application mapping), as well as configure the LoginURL 
inside of CustomAuth.ini. In other words, following the instructions inside 
of CustomAuth.ini

Since CustomAuth ISAPI is an arbitrary sample ISAPI DLL, there are no 
expectations that it reports issues anywhere other than signs that it 
manipulated requests on the server. You can turn on ETW Tracing in SP1 to 
track of it got loaded, or attach a debugger and wait on CustomAuth 
entrypoints like CustomAuth!GetExtensionVersion and 
CustomAuth!GetFilterVersion for proof of loading, or 
CustomAuth!HttpExtensionProc and CustomAuth!HttpFilterProc for proof of 
execution, or you can run tasklist /m CustomAuth.dll  to see if any 
processes have it loaded.

-- 
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"Dan"  wrote in message 
news:e89Of4eHGHA.2668@tk2msftngp13.phx.gbl...
> Ok, now that I have definitely installed it as an ISAPI Filter and a 
> Wildcard Script map, I still have no indication that it is attempting to 
> run.
>
> I've tried restarting IIS, and rebooting the server, nothing.  I don't get 
> any errors but I'm not prompted either, and the Event Log doesn't report 
> anything.
>
> The only websites on the server are "Default Web Site", and "Microsoft 
> SharePoint Administration" (not sure why that's there as Sharepoint isn't 
> installed but anyway...).
>
> "Default Web Site" has one virtual directory named "Test".
>
> I installed CustomAuth as an ISAPI filter and Wildcard Script Map on 
> "Default Web Site".  And the "Test" virtual directory inherited the 
> Wildcard Script Map.  The Default Web Site already had an ISAPI filter 
> named "fpexedll.dll", I believe that's for FrontPage Server Extensions.
>
> Any ideas?
>
> Thanks,
> Dan
>
> "David Wang [Msft]"  wrote in message 
> news:%23Wd2d$VHGHA.3000@TK2MSFTNGP14.phx.gbl...
>> You need to install CustomAuth.dll as global ISAPI Filter, and also 
>> install it as wildcard application mapping at the parent node of the URL 
>> namespace you want to protect. Since you installed global ISAPI Filter, 
>> you need to either recycle the Application Pool serving the URL namespace 
>> being protected, or restart IIS if running in IIS5 Compatibility Mode.
>>
>> Installing as a wildcard application mapping does not guarantee that it 
>> runs due to how application mappings work. You need to make sure that the 
>> applicable mapping is "active" at the URL namespace, either through 
>> inheritance (default) or explicit setting (if you've customized).
>>
>> -- 
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>> //
>>
>> "Dan"  wrote in message 
>> news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>>>I followed the instructions for installing the CustomAuth.dll as an ISAPI 
>>>filer at 
>>>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO. 
>>>The server I'm playing with does not have Sharepoint Portal Server 
>>>installed.  I simply want to experiment with CustomAuth.dll as a method 
>>>of authentication for a website.
>>>
>>> I downloaded the source code, built the dll, and installed it as an 
>>> ISAPI filter for a website in IIS (Windows 2003 Server with IIS 6.0). 
>>> The site only allows anonymous access but the CustomAuth.dll has no 
>>> effect.  I'm not getting any errors, but I'm not being redirected to the 
>>> default login form either.  I basically have no indication that it's 
>>> even attempting to run.
>>>
>>> I've tried installing it as a wildcard script map as well with the same 
>>> result.
>>>
>>> I've looked around and it seems other people have got it to run no 
>>> problem. What am I doing wrong?
>>>
>>> Any help would be very much appreciated.
>>>
>>> Thanks,
>>> Dan
>>>
>>
>>
>
>

Thanks for the response.

Only Anonymous access is enabled on the websites that I want CustomAuth to 
be active on (in this case simply the "default" website).

The ini file is using the default settings.  UseBuiltInLogonPage is set to 
1.

How do I turn on ETW tracing?  I'm a web developer for the most part (C#, 
ASP.Net, VB.Net, classic ASP etc.), so I don't have much experience coding 
with Visual C++ or using ISAPI filters. Thank you for your help.

Thanks,
Dan

"David Wang [Msft]"  wrote in message 
news:%23JubIDGIGHA.344@TK2MSFTNGP11.phx.gbl...
> Sharepoint website and fpexedll.dll exists because Windows Sharepoint is 
> installed.
>
> Did you also make sure that ONLY anonymous authentication is enabled 
> everywhere that you want CustomAuth to be active (and have CustomAuth.dll 
> active as a wildcard application mapping), as well as configure the 
> LoginURL inside of CustomAuth.ini. In other words, following the 
> instructions inside of CustomAuth.ini
>
> Since CustomAuth ISAPI is an arbitrary sample ISAPI DLL, there are no 
> expectations that it reports issues anywhere other than signs that it 
> manipulated requests on the server. You can turn on ETW Tracing in SP1 to 
> track of it got loaded, or attach a debugger and wait on CustomAuth 
> entrypoints like CustomAuth!GetExtensionVersion and 
> CustomAuth!GetFilterVersion for proof of loading, or 
> CustomAuth!HttpExtensionProc and CustomAuth!HttpFilterProc for proof of 
> execution, or you can run tasklist /m CustomAuth.dll  to see if any 
> processes have it loaded.
>
> -- 
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
> //
>
> "Dan"  wrote in message 
> news:e89Of4eHGHA.2668@tk2msftngp13.phx.gbl...
>> Ok, now that I have definitely installed it as an ISAPI Filter and a 
>> Wildcard Script map, I still have no indication that it is attempting to 
>> run.
>>
>> I've tried restarting IIS, and rebooting the server, nothing.  I don't 
>> get any errors but I'm not prompted either, and the Event Log doesn't 
>> report anything.
>>
>> The only websites on the server are "Default Web Site", and "Microsoft 
>> SharePoint Administration" (not sure why that's there as Sharepoint isn't 
>> installed but anyway...).
>>
>> "Default Web Site" has one virtual directory named "Test".
>>
>> I installed CustomAuth as an ISAPI filter and Wildcard Script Map on 
>> "Default Web Site".  And the "Test" virtual directory inherited the 
>> Wildcard Script Map.  The Default Web Site already had an ISAPI filter 
>> named "fpexedll.dll", I believe that's for FrontPage Server Extensions.
>>
>> Any ideas?
>>
>> Thanks,
>> Dan
>>
>> "David Wang [Msft]"  wrote in message 
>> news:%23Wd2d$VHGHA.3000@TK2MSFTNGP14.phx.gbl...
>>> You need to install CustomAuth.dll as global ISAPI Filter, and also 
>>> install it as wildcard application mapping at the parent node of the URL 
>>> namespace you want to protect. Since you installed global ISAPI Filter, 
>>> you need to either recycle the Application Pool serving the URL 
>>> namespace being protected, or restart IIS if running in IIS5 
>>> Compatibility Mode.
>>>
>>> Installing as a wildcard application mapping does not guarantee that it 
>>> runs due to how application mappings work. You need to make sure that 
>>> the applicable mapping is "active" at the URL namespace, either through 
>>> inheritance (default) or explicit setting (if you've customized).
>>>
>>> -- 
>>> //David
>>> IIS
>>> http://blogs.msdn.com/David.Wang
>>> This posting is provided "AS IS" with no warranties, and confers no 
>>> rights.
>>> //
>>>
>>> "Dan"  wrote in message 
>>> news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>>>>I followed the instructions for installing the CustomAuth.dll as an 
>>>>ISAPI filer at 
>>>>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO. 
>>>>The server I'm playing with does not have Sharepoint Portal Server 
>>>>installed.  I simply want to experiment with CustomAuth.dll as a method 
>>>>of authentication for a website.
>>>>
>>>> I downloaded the source code, built the dll, and installed it as an 
>>>> ISAPI filter for a website in IIS (Windows 2003 Server with IIS 6.0). 
>>>> The site only allows anonymous access but the CustomAuth.dll has no 
>>>> effect.  I'm not getting any errors, but I'm not being redirected to 
>>>> the default login form either.  I basically have no indication that 
>>>> it's even attempting to run.
>>>>
>>>> I've tried installing it as a wildcard script map as well with the same 
>>>> result.
>>>>
>>>> I've looked around and it seems other people have got it to run no 
>>>> problem. What am I doing wrong?
>>>>
>>>> Any help would be very much appreciated.
>>>>
>>>> Thanks,
>>>> Dan
>>>>
>>>
>>>
>>
>>
>
>

Does the filter part ever run ? If you look in the ISAPI filter list for the 
site, does the filter show up with a status ? Is that status active or not ? 
The filter does the redirection to the extension and  the extension handles 
the logon pieces. Can you get it running in the debugger as a filter or as 
an extension ?



"Dan"  wrote in message 
news:%23aEP00DIGHA.2680@TK2MSFTNGP09.phx.gbl...
>I have and it is set to be allowed in the Web Service Extensions folder but 
>I don't have any indication that it is attempting to run.
>
> Any ideas?
>
> Thanks,
> Dan
>
> "Robert Ginsburg"  wrote in message 
> news:OzldIloHGHA.3944@tk2msftngp13.phx.gbl...
>> Perhaps silly but have you checked the Web Service Extensions section to 
>> see if ISAPI Extensions are allowed or not ? I dont know if registering 
>> it qualifies as makeing it "known".
>>
>>
>>
>> "Dan"  wrote in message 
>> news:1CEADFFC-13E6-4CE4-B068-096DFB2EC3C8@microsoft.com...
>>> Ok, now that I have definitely installed it as an ISAPI Filter and a
>>> Wildcard Script map, I still have no indication that it is attempting to
>>> run.
>>>
>>> I've tried restarting IIS, and rebooting the server, nothing.  I don't 
>>> get
>>> any errors but I'm not prompted either, and the Event Log doesn't report
>>> anything.
>>>
>>> The only websites on the server are "Default Web Site", and "Microsoft
>>> SharePoint Administration" (not sure why that's there as Sharepoint 
>>> isn't
>>> installed but anyway...).
>>>
>>> "Default Web Site" has one virtual directory named "Test".
>>>
>>> I installed CustomAuth as an ISAPI filter and Wildcard Script Map on
>>> "Default Web Site".  And the "Test" virtual directory inherited the 
>>> Wildcard
>>> Script Map.  The Default Web Site already had an ISAPI filter named
>>> "fpexedll.dll", I believe that's for FrontPage Server Extensions.
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> Dan
>>>
>>>
>>> "Dan" wrote:
>>>
>>>> Oops, that was embarassing.
>>>>
>>>> Thanks for the help.
>>>>
>>>>
>>>> "David Wang [Msft]"  wrote in message
>>>> news:ODYc7QWHGHA.3728@tk2msftngp13.phx.gbl...
>>>> > You are not adding a wildcard application mapping. You have been 
>>>> > mapping a
>>>> > Script Engine to a URL with an extension of %.
>>>> >
>>>> > Inside the same Configuration tab, where the Application Mappings are 
>>>> > on
>>>> > top - the Wildcard Application Mappings are on the bottom. You click
>>>> > "Insert" to add.
>>>> >
>>>> > -- 
>>>> > //David
>>>> > IIS
>>>> > http://blogs.msdn.com/David.Wang
>>>> > This posting is provided "AS IS" with no warranties, and confers no
>>>> > rights.
>>>> > //
>>>> >
>>>> > "Dan"  wrote in message
>>>> > news:%238F6dDWHGHA.1452@TK2MSFTNGP11.phx.gbl...
>>>> >> After looking at further, I want to make sure I'm installing the dll
>>>> >> correctly as a wildcard script map.
>>>> >>
>>>> >> IIS->website->properties->Home Directory->Configuration->Add
>>>> >>
>>>> >> In the Add dialog I use the browse button to select the 
>>>> >> CustomAuth.dll
>>>> >>
>>>> >> I leave the radio button set to "All Verbs".
>>>> >>
>>>> >> I leave the "Script engine" checkbox checked.
>>>> >>
>>>> >> I uncheck the "Check that file exists" checkbox.
>>>> >>
>>>> >> What do I put in the extension text box?  Since it's suppose to be a
>>>> >> wildcard script map I had been trying "%".
>>>> >>
>>>> >> Is this correct so far?
>>>> >>
>>>> >> Thanks,
>>>> >> Dan
>>>> >>
>>>> >> "Dan"  wrote in message
>>>> >> news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>>>> >>>I followed the instructions for installing the CustomAuth.dll as an 
>>>> >>>ISAPI
>>>> >>>filer at
>>>> >>>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO.
>>>> >>>The server I'm playing with does not have Sharepoint Portal Server
>>>> >>>installed.  I simply want to experiment with CustomAuth.dll as a 
>>>> >>>method
>>>> >>>of authentication for a website.
>>>> >>>
>>>> >>> I downloaded the source code, built the dll, and installed it as an
>>>> >>> ISAPI filter for a website in IIS (Windows 2003 Server with IIS 
>>>> >>> 6.0).
>>>> >>> The site only allows anonymous access but the CustomAuth.dll has no
>>>> >>> effect.  I'm not getting any errors, but I'm not being redirected 
>>>> >>> to the
>>>> >>> default login form either.  I basically have no indication that 
>>>> >>> it's
>>>> >>> even attempting to run.
>>>> >>>
>>>> >>> I've tried installing it as a wildcard script map as well with the 
>>>> >>> same
>>>> >>> result.
>>>> >>>
>>>> >>> I've looked around and it seems other people have got it to run no
>>>> >>> problem. What am I doing wrong?
>>>> >>>
>>>> >>> Any help would be very much appreciated.
>>>> >>>
>>>> >>> Thanks,
>>>> >>> Dan
>>>> >>>
>>>> >>
>>>> >>
>>>> >
>>>> >
>>>>
>>>>
>>>>
>>
>>
>
>

In that case, turning on ETW tracing is not going to help much.

http://blogs.msdn.com/david.wang/archive/2006/01/24/HOWTO_Install_and_Use_CustomAuth_on_IIS_6.aspx

It pretty much worked out of the box for me after all the configuration is 
done. I only changed UseSSLForFormSubmission=0 to not require SSL for the 
login page (for testing) and I made sure that the website is Anonymous Auth 
only because CustomAuth code says that it will skip functionality if it 
detects other authentication protocols active.

-- 
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"Dan"  wrote in message 
news:eOt$HmGIGHA.240@TK2MSFTNGP11.phx.gbl...
> Thanks for the response.
>
> Only Anonymous access is enabled on the websites that I want CustomAuth to 
> be active on (in this case simply the "default" website).
>
> The ini file is using the default settings.  UseBuiltInLogonPage is set to 
> 1.
>
> How do I turn on ETW tracing?  I'm a web developer for the most part (C#, 
> ASP.Net, VB.Net, classic ASP etc.), so I don't have much experience coding 
> with Visual C++ or using ISAPI filters. Thank you for your help.
>
> Thanks,
> Dan
>
> "David Wang [Msft]"  wrote in message 
> news:%23JubIDGIGHA.344@TK2MSFTNGP11.phx.gbl...
>> Sharepoint website and fpexedll.dll exists because Windows Sharepoint is 
>> installed.
>>
>> Did you also make sure that ONLY anonymous authentication is enabled 
>> everywhere that you want CustomAuth to be active (and have CustomAuth.dll 
>> active as a wildcard application mapping), as well as configure the 
>> LoginURL inside of CustomAuth.ini. In other words, following the 
>> instructions inside of CustomAuth.ini
>>
>> Since CustomAuth ISAPI is an arbitrary sample ISAPI DLL, there are no 
>> expectations that it reports issues anywhere other than signs that it 
>> manipulated requests on the server. You can turn on ETW Tracing in SP1 to 
>> track of it got loaded, or attach a debugger and wait on CustomAuth 
>> entrypoints like CustomAuth!GetExtensionVersion and 
>> CustomAuth!GetFilterVersion for proof of loading, or 
>> CustomAuth!HttpExtensionProc and CustomAuth!HttpFilterProc for proof of 
>> execution, or you can run tasklist /m CustomAuth.dll  to see if any 
>> processes have it loaded.
>>
>> -- 
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>> //
>>
>> "Dan"  wrote in message 
>> news:e89Of4eHGHA.2668@tk2msftngp13.phx.gbl...
>>> Ok, now that I have definitely installed it as an ISAPI Filter and a 
>>> Wildcard Script map, I still have no indication that it is attempting to 
>>> run.
>>>
>>> I've tried restarting IIS, and rebooting the server, nothing.  I don't 
>>> get any errors but I'm not prompted either, and the Event Log doesn't 
>>> report anything.
>>>
>>> The only websites on the server are "Default Web Site", and "Microsoft 
>>> SharePoint Administration" (not sure why that's there as Sharepoint 
>>> isn't installed but anyway...).
>>>
>>> "Default Web Site" has one virtual directory named "Test".
>>>
>>> I installed CustomAuth as an ISAPI filter and Wildcard Script Map on 
>>> "Default Web Site".  And the "Test" virtual directory inherited the 
>>> Wildcard Script Map.  The Default Web Site already had an ISAPI filter 
>>> named "fpexedll.dll", I believe that's for FrontPage Server Extensions.
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> Dan
>>>
>>> "David Wang [Msft]"  wrote in message 
>>> news:%23Wd2d$VHGHA.3000@TK2MSFTNGP14.phx.gbl...
>>>> You need to install CustomAuth.dll as global ISAPI Filter, and also 
>>>> install it as wildcard application mapping at the parent node of the 
>>>> URL namespace you want to protect. Since you installed global ISAPI 
>>>> Filter, you need to either recycle the Application Pool serving the URL 
>>>> namespace being protected, or restart IIS if running in IIS5 
>>>> Compatibility Mode.
>>>>
>>>> Installing as a wildcard application mapping does not guarantee that it 
>>>> runs due to how application mappings work. You need to make sure that 
>>>> the applicable mapping is "active" at the URL namespace, either through 
>>>> inheritance (default) or explicit setting (if you've customized).
>>>>
>>>> -- 
>>>> //David
>>>> IIS
>>>> http://blogs.msdn.com/David.Wang
>>>> This posting is provided "AS IS" with no warranties, and confers no 
>>>> rights.
>>>> //
>>>>
>>>> "Dan"  wrote in message 
>>>> news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>>>>>I followed the instructions for installing the CustomAuth.dll as an 
>>>>>ISAPI filer at 
>>>>>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO. 
>>>>>The server I'm playing with does not have Sharepoint Portal Server 
>>>>>installed.  I simply want to experiment with CustomAuth.dll as a method 
>>>>>of authentication for a website.
>>>>>
>>>>> I downloaded the source code, built the dll, and installed it as an 
>>>>> ISAPI filter for a website in IIS (Windows 2003 Server with IIS 6.0). 
>>>>> The site only allows anonymous access but the CustomAuth.dll has no 
>>>>> effect.  I'm not getting any errors, but I'm not being redirected to 
>>>>> the default login form either.  I basically have no indication that 
>>>>> it's even attempting to run.
>>>>>
>>>>> I've tried installing it as a wildcard script map as well with the 
>>>>> same result.
>>>>>
>>>>> I've looked around and it seems other people have got it to run no 
>>>>> problem. What am I doing wrong?
>>>>>
>>>>> Any help would be very much appreciated.
>>>>>
>>>>> Thanks,
>>>>> Dan
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Thank you so much!

After all this it turned out that I just needed to deny anonymous user 
access to the actual file or directory.  I think I was getting confused 
because the website in IIS needs to ONLY have anonymous access checked, but 
the actual directory or file you want protected needs to deny anonymous 
access.  And, if I'm understanding it correctly, a custom login page would 
need to allow anonymous access.

Thanks again,
Dan

"David Wang [Msft]"  wrote in message 
news:OJv%23EGUIGHA.528@TK2MSFTNGP12.phx.gbl...
> In that case, turning on ETW tracing is not going to help much.
>
> http://blogs.msdn.com/david.wang/archive/2006/01/24/HOWTO_Install_and_Use_CustomAuth_on_IIS_6.aspx
>
> It pretty much worked out of the box for me after all the configuration is 
> done. I only changed UseSSLForFormSubmission=0 to not require SSL for the 
> login page (for testing) and I made sure that the website is Anonymous 
> Auth only because CustomAuth code says that it will skip functionality if 
> it detects other authentication protocols active.
>
> -- 
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
> //
>
> "Dan"  wrote in message 
> news:eOt$HmGIGHA.240@TK2MSFTNGP11.phx.gbl...
>> Thanks for the response.
>>
>> Only Anonymous access is enabled on the websites that I want CustomAuth 
>> to be active on (in this case simply the "default" website).
>>
>> The ini file is using the default settings.  UseBuiltInLogonPage is set 
>> to 1.
>>
>> How do I turn on ETW tracing?  I'm a web developer for the most part (C#, 
>> ASP.Net, VB.Net, classic ASP etc.), so I don't have much experience 
>> coding with Visual C++ or using ISAPI filters. Thank you for your help.
>>
>> Thanks,
>> Dan
>>
>> "David Wang [Msft]"  wrote in message 
>> news:%23JubIDGIGHA.344@TK2MSFTNGP11.phx.gbl...
>>> Sharepoint website and fpexedll.dll exists because Windows Sharepoint is 
>>> installed.
>>>
>>> Did you also make sure that ONLY anonymous authentication is enabled 
>>> everywhere that you want CustomAuth to be active (and have 
>>> CustomAuth.dll active as a wildcard application mapping), as well as 
>>> configure the LoginURL inside of CustomAuth.ini. In other words, 
>>> following the instructions inside of CustomAuth.ini
>>>
>>> Since CustomAuth ISAPI is an arbitrary sample ISAPI DLL, there are no 
>>> expectations that it reports issues anywhere other than signs that it 
>>> manipulated requests on the server. You can turn on ETW Tracing in SP1 
>>> to track of it got loaded, or attach a debugger and wait on CustomAuth 
>>> entrypoints like CustomAuth!GetExtensionVersion and 
>>> CustomAuth!GetFilterVersion for proof of loading, or 
>>> CustomAuth!HttpExtensionProc and CustomAuth!HttpFilterProc for proof of 
>>> execution, or you can run tasklist /m CustomAuth.dll  to see if any 
>>> processes have it loaded.
>>>
>>> -- 
>>> //David
>>> IIS
>>> http://blogs.msdn.com/David.Wang
>>> This posting is provided "AS IS" with no warranties, and confers no 
>>> rights.
>>> //
>>>
>>> "Dan"  wrote in message 
>>> news:e89Of4eHGHA.2668@tk2msftngp13.phx.gbl...
>>>> Ok, now that I have definitely installed it as an ISAPI Filter and a 
>>>> Wildcard Script map, I still have no indication that it is attempting 
>>>> to run.
>>>>
>>>> I've tried restarting IIS, and rebooting the server, nothing.  I don't 
>>>> get any errors but I'm not prompted either, and the Event Log doesn't 
>>>> report anything.
>>>>
>>>> The only websites on the server are "Default Web Site", and "Microsoft 
>>>> SharePoint Administration" (not sure why that's there as Sharepoint 
>>>> isn't installed but anyway...).
>>>>
>>>> "Default Web Site" has one virtual directory named "Test".
>>>>
>>>> I installed CustomAuth as an ISAPI filter and Wildcard Script Map on 
>>>> "Default Web Site".  And the "Test" virtual directory inherited the 
>>>> Wildcard Script Map.  The Default Web Site already had an ISAPI filter 
>>>> named "fpexedll.dll", I believe that's for FrontPage Server Extensions.
>>>>
>>>> Any ideas?
>>>>
>>>> Thanks,
>>>> Dan
>>>>
>>>> "David Wang [Msft]"  wrote in message 
>>>> news:%23Wd2d$VHGHA.3000@TK2MSFTNGP14.phx.gbl...
>>>>> You need to install CustomAuth.dll as global ISAPI Filter, and also 
>>>>> install it as wildcard application mapping at the parent node of the 
>>>>> URL namespace you want to protect. Since you installed global ISAPI 
>>>>> Filter, you need to either recycle the Application Pool serving the 
>>>>> URL namespace being protected, or restart IIS if running in IIS5 
>>>>> Compatibility Mode.
>>>>>
>>>>> Installing as a wildcard application mapping does not guarantee that 
>>>>> it runs due to how application mappings work. You need to make sure 
>>>>> that the applicable mapping is "active" at the URL namespace, either 
>>>>> through inheritance (default) or explicit setting (if you've 
>>>>> customized).
>>>>>
>>>>> -- 
>>>>> //David
>>>>> IIS
>>>>> http://blogs.msdn.com/David.Wang
>>>>> This posting is provided "AS IS" with no warranties, and confers no 
>>>>> rights.
>>>>> //
>>>>>
>>>>> "Dan"  wrote in message 
>>>>> news:u0VRVSVHGHA.2036@TK2MSFTNGP14.phx.gbl...
>>>>>>I followed the instructions for installing the CustomAuth.dll as an 
>>>>>>ISAPI filer at 
>>>>>>http://www.theserverside.net/articles/showarticle.tss?id=ImplementingSSO. 
>>>>>>The server I'm playing with does not have Sharepoint Portal Server 
>>>>>>installed.  I simply want to experiment with CustomAuth.dll as a 
>>>>>>method of authentication for a website.
>>>>>>
>>>>>> I downloaded the source code, built the dll, and installed it as an 
>>>>>> ISAPI filter for a website in IIS (Windows 2003 Server with IIS 6.0). 
>>>>>> The site only allows anonymous access but the CustomAuth.dll has no 
>>>>>> effect.  I'm not getting any errors, but I'm not being redirected to 
>>>>>> the default login form either.  I basically have no indication that 
>>>>>> it's even attempting to run.
>>>>>>
>>>>>> I've tried installing it as a wildcard script map as well with the 
>>>>>> same result.
>>>>>>
>>>>>> I've looked around and it seems other people have got it to run no 
>>>>>> problem. What am I doing wrong?
>>>>>>
>>>>>> Any help would be very much appreciated.
>>>>>>
>>>>>> Thanks,
>>>>>> Dan
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>