I want to add a web service to an existing site that was deployed as an "Install" version of DNN. This web service will expose a method that will take a Username and Password and return whether it is a valid DNN User. At this point I am NOT concerned about security risks and such, this is a non-production DNN site and this is simply a proof-of-concept project.

I have successfully done this with a simple website (not DNN) that I added a few users to and then I added a virtual directory to this website, created an application, copied in my web service to that new application, set it's Provider to access the parent site's aspnetsqlprovider database and everything worked fine. I was able to verify through the web service whether the test user/pass were valid.

When I try the same process with a DNN site, it seems to be ignoring the web.config of the new virtual directory/application and it starts throwing errors about httpmodules and such from the DNN site's web.config.

I have tried using location path elements in the DNN web.config but either I'm not understanding the process well enough (very likely) or it just isn't working.

Anyone have any ideas what I'm doing wrong here?