none
Secure=1 failed because the request was unable to reply to an HTTP 401 request from application RRS feed

  • Question

  • All

    We are publishing internal App via UAG2010. App is working till sub component which is coded with Ajax enabled websersvices. Error message is 24 from UAG web monitor

    The request from user domain.org\usser at source IP address A.b.c.d to trunk dotcomtest; Secure=1 failed because the request was unable to reply to an HTTP 401 request from application WebApp of type testWebApp. The session ID is 6DC79D89-8DD9-4B53-BFC8-256108525AD9.

    we tried SSO and no SSO. It still show the above error messages. SSO is working after login to UAG. Authentication is selected 401 and NTLM (both).  we think it is because of Ajax coding. Does anyone have any suggestion  and direction

    thank you


    Daniel

    Thursday, June 7, 2012 8:28 PM

All replies

  • Hi,

    The key thing in web publishing is always to understand how the application works, which mean, get a trace (HTTPwatch if you bought it, or Fiddler which is free). Of course if you are not familiar with HTTP and reverse engineering, could be a bit complex the first time but that worth it.

    A good start would be to capture this traffic on the LAN (without UAG). So you will be able to see how the appliction ask for authentication (FIM, NTLM, Cleartext)... and of course see if you have other 401 because of Ajax. "Code" in an HTML page is by definition not predictable, human decision, ...

    One of the frequent problem with Ajax is that the "page" is "finished" (URL generation, ... etc) by the code on the client side, and because code is not predictable (not a HREF link), part of the URLs are not translated. That is general feedback.

    Capturing the traffic and looking at the HTTP dialog is a good start. Then you can "guess" what to change in the configuration in UAG.

    Regards.


    Frederic (MSFT)

    Friday, June 8, 2012 7:21 AM