Security Header update

mphilip

We currently integrate with Web Service: 2011-09-01, and we are in the process of updating the security header to include the Type attribute to the Password element.

The current end point we use is :

https://idtlab-uat.hostedtax.thomsonreuters.com/sabrix/services/taxcalculationservice/2011-09-01/

Notice it says 2011-09-01. When referring to the playbook available from this portal this is the end point that is specified

https://partnerdev2-uat.hostedtax.thomsonre uters.com/sabrix/services/taxservice/2009-12 -20/taxservice

Based on playbook, and security header update documentation I updated the request to incluide the following:

- Attribute Type to Password element

- Added TimeStamp element

<soapenv:Envelope xmlns:ns="http://www.sabrix.com/services/taxcalculationservice/2011-09-01" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">;
<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" soapenv:mustUnderstand="1">
<wsse:UsernameToken>
<wsse:Username>DevCom</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">4TaxCalc</wsse:Password>;
<wsu:Timestamp wsu:Id="Timestamp-1">
<wsu:Created>2017-08-06T15:03:06.021Z</wsu:Created>
<wsu:Expires>2017-08-06T16:08:06.021Z</wsu:Expires>
</wsu:Timestamp>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
<soapenv:Body>
<ns:taxCalculationRequest xmlns:ns="http://www.sabrix.com/services/taxcalculationservice/2011-09-01">;
<ns:INDATA version="G">
<ns:COMPANY_NAME>SciQuest</ns:COMPANY_NAME>
<ns:EXTERNAL_COMPANY_ID>DevCom_US</ns:EXTERNAL_COMPANY_ID>
<ns:INVOICE>
<ns:CALCULATION_DIRECTION>F</ns:CALCULATION_DIRECTION>
<ns:COMPANY_ROLE>S</ns:COMPANY_ROLE>
<ns:CURRENCY_CODE>USD</ns:CURRENCY_CODE>
<ns:INVOICE_DATE>2014-08-26</ns:INVOICE_DATE>
<ns:INVOICE_NUMBER>353027</ns:INVOICE_NUMBER>
<ns:TRANSACTION_TYPE>GS</ns:TRANSACTION_TYPE>
<ns:USER_ELEMENT>
<ns:NAME>ATTRIBUTE3</ns:NAME>
<ns:VALUE>Blanket order test</ns:VALUE>
</ns:USER_ELEMENT>
<ns:USER_ELEMENT>
<ns:NAME>ATTRIBUTE2</ns:NAME>
<ns:VALUE>Blanket order test</ns:VALUE>
</ns:USER_ELEMENT>
<ns:USER_ELEMENT>
<ns:NAME>ATTRIBUTE1</ns:NAME>
<ns:VALUE>Blanket order test</ns:VALUE>
</ns:USER_ELEMENT>
<ns:LINE ID="1">
<ns:COMMODITY_CODE />
<ns:DESCRIPTION>test</ns:DESCRIPTION>
<ns:GROSS_AMOUNT>121.0</ns:GROSS_AMOUNT>
<ns:LINE_NUMBER>1</ns:LINE_NUMBER>
<ns:PRODUCT_CODE>1234</ns:PRODUCT_CODE>
<ns:SHIP_TO>
<ns:COUNTRY>US</ns:COUNTRY>
<ns:STATE>NC</ns:STATE>
<ns:CITY>Cary</ns:CITY>
<ns:POSTCODE>27513</ns:POSTCODE>
</ns:SHIP_TO>
<ns:USER_ELEMENT>
<ns:NAME>ATTRIBUTE3</ns:NAME>
<ns:VALUE>true</ns:VALUE>
</ns:USER_ELEMENT>
<ns:USER_ELEMENT>
<ns:NAME>ATTRIBUTE2</ns:NAME>
<ns:VALUE>true</ns:VALUE>
</ns:USER_ELEMENT>
<ns:USER_ELEMENT>
<ns:NAME>ATTRIBUTE1</ns:NAME>
<ns:VALUE>true</ns:VALUE>
</ns:USER_ELEMENT>
</ns:LINE>
<ns:LINE ID="2">
<ns:COMMODITY_CODE />
<ns:DESCRIPTION>test</ns:DESCRIPTION>
<ns:GROSS_AMOUNT>132.0</ns:GROSS_AMOUNT>
<ns:LINE_NUMBER>2</ns:LINE_NUMBER>
<ns:PRODUCT_CODE>1234</ns:PRODUCT_CODE>
<ns:SHIP_TO>
<ns:COUNTRY>US</ns:COUNTRY>
<ns:STATE>NC</ns:STATE>
<ns:CITY>Cary</ns:CITY>
<ns:POSTCODE>27513</ns:POSTCODE>
</ns:SHIP_TO>
<ns:USER_ELEMENT>
<ns:NAME>ATTRIBUTE3</ns:NAME>
<ns:VALUE>true</ns:VALUE>
</ns:USER_ELEMENT>
<ns:USER_ELEMENT>
<ns:NAME>ATTRIBUTE2</ns:NAME>
<ns:VALUE>true</ns:VALUE>
</ns:USER_ELEMENT>
<ns:USER_ELEMENT>
<ns:NAME>ATTRIBUTE1</ns:NAME>
<ns:VALUE>true</ns:VALUE>
</ns:USER_ELEMENT>
</ns:LINE>
</ns:INVOICE>
</ns:INDATA>
</ns:taxCalculationRequest>
</soapenv:Body>
</soapenv:Envelope>

In SoapUI when I try to send this response to the end point : https://partnerdev2-uat.hostedtax.thomsonre uters.com/sabrix/services/taxservice/2009-12 -20/taxservice

I do not get a response, SoapUI displays "Error getting response."

Dipti.Arora

@mphilip Could you please email us the corresponding xml at IDTDevelopmentPartnerProgram@thomsonreuters.com so that we can take a look. Thanks.

Dipti.Arora

This request was a specific scenario on Tax calculation Service and was resolved with our Partner. In the future we will have troubleshooting topics within our API family that may help community members. Thank you.

IDTDevelopmentPartnerProgram

This is a test