2 Replies Latest reply on Apr 19, 2012 3:51 AM by bdoyle

    Sage Application not working via Web Gateway

    bdoyle

      Hi Guys,

       

      We're having an issue with our Webgateway. We are trying to access a Sage payroll application. The application connects to a licencing server in Sage when it runs. However, when running via the Web Gateway, it does not work. THis is a WebGateway V 7.1, and the system is running Windows 7. Below is the extract from the log files relating to the site.

       

      [18/Apr/2012:12:00:42+0000] "" *.*.*.* 407 "CONNECT https://licensing.services.sage.comHTTP/1.1" "" "-" "" 2812 """" "0"
      [18/Apr/2012:12:00:42 +0000] "" *.*.*.* 407 "CONNECT https://licensing.services.sage.comHTTP/1.1" "" "-" "" 2812 """"

       

      We have added the site and the IP address to the Global Whitelist, but this has made no difference.

       

      If anyone could point me in the right direcetion on how to get this working, I'd appreciate it!

       

      -Brian


        • 1. Re: Sage Application not working via Web Gateway
          asabban

          Hello,

           

          407 means that MWG wants this request authenticated. Typically for NTLM Authentication you may have up to two lines with 407 before there is a line with a status code of 200.

           

          Can you verify there are requests to the same URL which do not have a 407 as a status code in the access.log? If there are some there is a different issue apart from authentication. If all are answered with 407 the application is most likely not able to authenticate, or is not configured to authenticate. In this case you could check whether you can specify username/passwort for the proxy somewhere in the application, or exclude the URL from your authentication rule set and see if this helps.

           

          Best,

          ANdre

          • 2. Re: Sage Application not working via Web Gateway
            bdoyle

            Hi Andre,

             

            Thanks for that. we have added the website to the Authentication whitelist, so it will not request authentication and also added the site to an application authentication whitelist we have created. The software can now access the required services without any issues.

             

            -Brian