locked
How to carry over the password in double hop? RRS feed

  • Question

  • Hello All, 

    This error was found in our SSRS (HA--High Availability) System. The HA design goes like this,

    The 3rd party tool has been used to round-robin the traffic to Node1 and Node2. For users, they access the application with a virtual name endpoint  let's say: https://V1/webApp. (V1 could reach Node 1 or Node 2 and must be one of them)

    The web Application and SSRS are deployed both on Node 1 and Node 2.

    On Node 1, The web application calls SSRS webservice by the virtual name given in config file https://v1/reportExecution2005.asmx, 

    On node2, we do the same way.

    Each time, when users hit V1, the traffic goes to web app on Node 1 and calls SSRS on node 2 SSRS execution endpoint, then we see this error, 

    request failed with HTTP status 401: Unauthorized. : System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
    
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
    
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

    The walk around is hard binding the webapp on Node1 only hits SSRS on Node1 and the same case for Node2. But doing so, we sacrifice the HA senario as this: if webAPP on Node1 is live but SSRS on Node1 is down, this HA case cannot be covered by configuring the N1-N1 and N2-N2 binding.   Still trying to look for a better way to make this happen Node 1 -->V1 and node 2-->V1.

    Who can share some ideas on this? What makes this distributed call fail?


    Derek

    Wednesday, April 23, 2014 10:51 PM

Answers