1 Reply Latest reply: May 19, 2014 4:44 PM by Adam Freseman RSS

    QMS API Service Key ticket in the SOAP header instead of the HTTP header?

      We are  integrating the QlikView 11 QMS web service API with a third party product that insists on generating the GetServices POST with the “Service Key”  ticket in the SOAP header instead of the HTTP header: 

       

      1) QlikView 11’s QMS web service API requires that the QlikView “Service-Key” Ticket be submitted, via a  GetServices POST, as part of the HTTP header

      2) We are using a third-party product that consumes the QMS WSDL without error; however the third-party product then  generates a GetServices POST with the Service-Key ticket in the SOAP header instead of the HTTP header

      3) We cannot change the way the third-party product generates the GetServices POST

      4) Can anyone provide a workaround that enables us to submit the Service-Key  ticket in the SOAP header when interacting with the QMS API?

       

      Here is an example:

       

       

       

      Third-party product's attempt to use consumed QMS WSDL; note the Service-Key is in the SOAP header; this is the issue

      POST /QMS/Service  HTTP/1.1

      Content-Type: text/xml;

      charset=utf-8

      SOAPAction: "http://ws.qliktech.com/QMS/11/IQMS/GetServices"

      Host: sabossqva01i:4799

      Content-Length: 328

      Expect: 100

      <s:Envelope xmlns: s="http://schemas.xmlsoap.org/soap/envelope/">

      <s:Header>

      <X-Service-Key xmlns="QMSAPI">GHidpfuD0zq1FR3eCxvuiikAhHoI+ad0</X-Service-Key>

      </s:Header>

      <s:Body>

      <GetServices xmlns="http://ws.qliktech.com/QMS/11/">

      <serviceTypes>QlikViewManagementService QlikViewServer</serviceTypes>

      </GetServices>

      </s:Body>

      </s:Envelope>

       

       

      For contrast, the following is an example of a well formed request with the Service-Key in the HTTP header:

      POST /QMS/Service HTTP/1.1

      Content-Type: text/xml;

      charset=utf-8

      X-Service-Key: QLQtiNm2/f9AV/0R7fbTkqvmIBQgqAlX

      SOAPAction: "http://ws.qliktech.com/QMS/11/IQMS/GetServices"

      Host: sabossqva01i:4799

      Content-Length: 203

      Expect: 100-continue

      Accept-Encoding: gzip, deflate

      <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

      <s:Body>

      <GetServices xmlns="http://ws.qliktech.com/QMS/11/">

      <serviceTypes>QlikViewServer</serviceTypes>

      </GetServices>

      </s:Body>

      </s:Envelope>

       

      Can anyone provide a workaround that enables us to submit the Service-Key  ticket in the SOAP header when interacting with the QMS API?

       

      Thanks for your help with this.