We are excited to announce that the IIS.NET Forums are moving to the new Microsoft Q&A experience. Learn more >

Authentication stops working in classic ASP PagesRSS

1 reply

Last post Sep 13, 2019 05:27 AM by Jalpa Panchal

  • Authentication stops working in classic ASP Pages

    Sep 12, 2019 04:10 PM|djcampos|LINK

    I've been using the same code for years in order to authenticate to Active Directory through my classic ASP pages for years without any problems.  We just moved to a new Windows 2019 server and the code still works, however, very intermittently the server will stop responding and when a user attempts to log in, they will receive an error message stating that the username or password is incorrect even when the submitted information is correct.  I will then restart the server and it starts working again.  This happens three or four times a day and has only happened on this new server.  I never had this problem with our old web server.  We've checked logs and running services but cannot find any problems.  We've stopped and restarted IIS but that doesn't seem to fix the problem either.  Any help pointing me in the right direction would be great!

  • Re: Authentication stops working in classic ASP Pages

    Sep 13, 2019 05:27 AM|Jalpa Panchal|LINK

    Hi,

    Could you share which iis version before you are using, sample code, web.config setting and which authentication you set, under which identity your application pool is running? 

    make sure you disabled anonymous authentication.


    <!-- web.config -->
    <configuration> <system.web> <authentication mode="Windows" /> <authorization> <allow roles="MYDOMAIN\MY-AD-GROUP" /> <deny users="*" /> </authorization> </system.web> </configuration>
    <!-- applicationHost.config -->
    <configuration>
      <location path="YOUR-APP">
        <system.webServer>
          <security>
            <authentication>
              <anonymousAuthentication enabled="false" />
              <windowsAuthentication enabled="true" />
            </authentication>
          </security>
        </system.webServer>
      </location>
    </configuration>

    and check the folder permission that user have enough permission to access it. 

    Regards,

    Jalpa

    .NET forums are moving to a new home on Microsoft Q&A, we encourage you to go to Microsoft Q&A for .NET for posting new questions and get involved today.