I have set up a website using IIS and ASP.NET which grants access to users using a separate authentication server.
Therefore, in the web.config of my website I've added a module, which is a separate, 3rd party dll and will be loaded first when a user connects to the website, and which provides a redirect to the authentication server and manages the access accordingly.
To do this, my website is set up to use Anonymous authentication, leaving everything in charge to the 3rd party dll.
From a user perspective, everything works fine: users cannot access the website content without having authenticated on the separate server; however, there are certain folders of the website which seem to be accessible to anyone without authenticating.
For instance, if my website is: Www.example.com/myWebsite/Default.aspx I have created a subfolder called "Temp": Www.example.com/myWebsite/Temp Where I store temporary files. I noticed that this folder "bypasses" the authentication logic above: anyone can go to, i.e. Www.example.com/myWebsite/Temp/file.txt And download such file without authenticating.
Am I missing some configuration of IIS? Or does it look like there is a security flaw in the 3rd party authentication dll?