<p>Hi,</p> <p>I'm pretty much a total newb to IIS and this is the first time I'm setting up a server for my organisation as my colleague that usually does this is currently not available.</p> <p>I'm currently trying to configure a site with 2 methods of secure/authenticated
access.</p> <p>So I have 2 applications set up in IIS both pointing to the same Physical Path</p> <p><a href="https://www.test.com/a">https://www.test.com/a</a> - uses Basic Auth with an IP address whitelist</p> <p>https://www.test.com/b- uses AD Auth</p><p>The idea being that</p> <p><a href="https://www.test.com/a">https://www.example.com/a</a> is ONLY accessible from a specific set of IP ranges using basic auth</p> <p>and</p> <p><a href="https://www.test.com/b">https://www.example.com/b</a> is ONLY accessible
using Active Directory</p> <p>The problem I have is that whilst <a href="https://www.test.com/a">https://www.example.com/a</a> appears to be working as intended <a href="https://www.test.com/b">https://www.example.com/b</a> will also allow for Basic auth as
they are sharing the same web.config file, so the AD auth falls back to basic auth - which isn't acceptable</p> <p>Is there anything I can do differently so they both work as intended?<br> Should I have this setup differently?</p> <p>Any ideas anyone?</p><p></p> <p>Thanks</p> <p></p> <p></p> <p></p>
↧