ASP.NET Identity - Are "web.config" files no longer acting in the capacity of a security guard for our ASP.NET applications files and folders?

With the introduction of the new and imrpoved "AspNet Identity" system I get the strange feeling that the traditional "web.config" files are being slowly put out to pasture. I have noticed that in a virgin project in "Visual Studio 2013" in the default "web.config" file it sets the authentication mode to "None" like so:
<system.web> <authentication mode="None" /> <compilation debug="true" targetFramework="4.5" /> <httpRuntime targetFramework="4.5" /> </system.web> So, with default authentication mode being set to the default of "None" does this mean that "web.config" files will no longer be used to filter user requests for specific files and folders?