Skip Navigation LinksHome Page > Forums > SpiraTeam Forums > SpiraTeam Issues & Qu... > SOAP v3.0 WS API issue "C...

SOAP v3.0 WS API issue "ContractFilter mismatch at the EndpointDispatcher"

Thursday, August 16, 2012

Hi

I can't figure out how to make the 3.0 SOAP API SpiraTeam v3.2 (011) | en to work. I have no problem with 2.2, but I need features of the 3.0.

I tested with http://soapclient.com/soapmsg.html

V 2.2

Server Address: http://my.spirateam-server.com/Services/v2_2/ImportExport.asmx
SOAPAction:    https://www.inflectra.com/SpiraTest/Services/v2.2/Connection_Authenticate
Request:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
    <Connection_Authenticate xmlns="https://www.inflectra.com/SpiraTest/Services/v2.2/">
      <userName>my.username</userName>
      <password>my.password</password>
    </Connection_Authenticate>
</soap:Body>
</soap:Envelope>
Result :
<soap:Envelope><soap:Body><Connection_AuthenticateResponse><Connection_AuthenticateResult>true</Connection_AuthenticateResult></Connection_AuthenticateResponse></soap:Body></soap:Envelope>

V 3.0

Server Address: http://my.spirateam-server.com/Services/v3_0/ImportExport.svc
SOAPAction: https://www.inflectra.com/SpiraTest/Services/v3.0/Connection_Authenticate
Request:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
    <Connection_Authenticate xmlns="https://www.inflectra.com/SpiraTest/Services/v3.0/">
      <userName>my.username</userName>
      <password>my.password</password>
    </Connection_Authenticate>
</soap:Body>
</soap:Envelope>
Result:
<s:Envelope><s:Body><s:Fault><faultcode>a:ActionNotSupported</faultcode><faultstring xml:lang="fr-FR">The message with Action 'https://www.inflectra.com/SpiraTest/Services/v3.0/Connection_Authenticate' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</faultstring></s:Fault></s:Body></s:Envelope>

Am I doing something wrong ? Is it a server setup issue ?

Any help is appreciated.

Thanks

4 Replies

Friday, August 17, 2012

inflectra.david

re: nicolas.bernier Thursday, August 16, 2012

Hi Nicolas

I tried using the Message Builder part of the tool (http://soapclient.com/soapmsg.html) where you enter in the WSDL:

http://my.spirateam-server.com/Services/v3_0/ImportExport.svc?wsdl

and it changed the SOAP Action to:

Server Address: http://my.spirateam-server.com/Services/v3_0/ImportExport.svc
SOAPAction: https://www.inflectra.com/SpiraTest/Services/v3.0/IService/Connection_Authenticate

and that appears to work, using the same Request body.

Monday, August 20, 2012

nicolas.bernier

re: inflectra.david Friday, August 17, 2012

Adam (Support)
and it changed the SOAP Action to:

SOAPAction: https://www.inflectra.com/SpiraTest/Services/v3.0/IService/Connection_Authenticate

and that appears to work, using the same Request body.

Thanks, it works for me too ! The /IService part was just missing in the action.

Wednesday, April 29, 2015

nilesh

re: nicolas.bernier Monday, August 20, 2012

NameSpace :- https://www.inflectra.com/SpiraTest/Services/v4_0/

Suffix :- /Services/v4_0/ImportExport.svc

Version :- 4.0

SOAPACTION :- https://www.inflectra.com/SpiraTest/Services/v4_0/TestRun_RecordAutomated2

Getting Output :-

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a="http://schemas.microsoft.com/ws/2005/05/addressing/none">a:ActionNotSupported</faultcode><faultstring xml:lang="en-US">The message with Action 'https://www.inflectra.com/SpiraTest/Services/v4_0/TestRun_RecordAutomated2' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</faultstring></s:Fault></s:Body></s:Envelope>

Wednesday, April 29, 2015

ICTL

re: nilesh Wednesday, April 29, 2015

Adam,

We have a similar problem here, with transaction IDs not being saved in 'Actual Results' after we click 'Pass'.

We're using soapclient to insert a transaction ID into a Spira Team Test Case result field.

SpiraTeam v4.1.0.6.

One user lost an entire days transaction ids bc they were not being saved.

Do you have any ideas/workaround for this? Best, Ruth

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885

Statistics

Started: Thursday, August 16, 2012
Last Reply: Wednesday, April 29, 2015
Replies: 4
Views: 14061

SOAP v3.0 WS API issue "ContractFilter mismatch at the EndpointDispatcher"

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

Edit Thread

Edit Message

Search Results