Forum Discussion

mbecker_309454's avatar
mbecker_309454
Icon for Nimbostratus rankNimbostratus
May 04, 2017

SOAP LTM/APM McKesson App issue

Using LTM as a proxy for a McKesson application, using a virtual server. The virtual server works well for the app, until we added a APM logon page, with simple End User Authentication. Once the Logon page is added I get these errors on the windows PC:

 

Msg="Error updating files: System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8

 

and

 

Msg="Failed to load xml: Error updating files: System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8

 

Looks like SOAP XML issue, where once I remove the Logon policy ( logon page and auth ) is get Msg="Loaded xml from I tried a client check and permitted non-browser with no logon page and still no luck.

 

Is there a setting for SOAP XML on the LTM Virtual or an iRule to permit SOAP XML ?

 

  • Is there a way to use clientless mode, after the first logon against the APM ? so that the local app client can connect to the web service...

     

  • Hi,

     

    what is the McKesson App behavior? does it authenticate with browser (with a logon page) or only with XML?

     

    is the user / password inside HTTP headers (Basic authentication) or inside XML parameters?

     

    if it is only with XML, you need to parse XML content to find user / password.

     

  • Hello,

     

    we have maybe not the same problem, but very similar. Our clinet is being using Salesforce cloud app that uses SOAP protocol. Goal is that client must be authenticated via client certificate, policy has been created, but looks like SAOP app is not able to read 302 redirect to /my.policy from APM. Did anyone come across similar issue? As a workaround we are using iRule, but would be great to have a solution for APM as well.

     

  • Hi dryk_00!

     

    Have you managed to fix the issue?

     

    I have the same "We are done!" problem and no idea how to deal with it.

     

    Thanks, Mikhail.