Anyone using Tradeshift with NAV2017?

pdj

I have tried to setup NAV2017CU10 and NAV2017CU14 to a Tradeshift sandbox account, as described here:
https://community.dynamics.com/nav/b/navvideos/archive/2015/12/22/how-do-i-use-document-exchange-service-to-send-amp-receive-invoices-in-microsoft-dynamics-nav

However, I keep getting this error when trying to test my connection:
"Authentication failed because the remote party has closed the transport stream."

When I try using NAV2018RTM and NAV2018CU1 and DevPreview it works fine.

Anyone with an idea on how to solve this issue? (without upgrading to NAV2018)

(My guess is that due to lacking support of TLS1.2 in NAV2017, but I'm unable to find any documentation)

pdj

The problem is fixed in the 2018 May CUs, but you will need to add this line to the CustomSettings.Config:

<add key="SecurityProtocol" value="Tls12"/>

mdPartnerNL

Yes, i could connect using NAV2017CU13 NL, but the problem with this version is the layout of the xml. Which could not be uploaded.

pdj

Really? I never get this far. Can you do at successful TestConnection to the sandbox API (https://api-sandbox.tradeshift.com/tradeshift/rest/external) or are you connecting to the Tradeshift production URL?

I can see Tradeshift has announced they are switching from TLS1.0 to TLS1.2 by the beginning of 2018 (https://nhssbs.support.tradeshift.com/knowledgebase/article/115000877644) but I don't know if they have done it yet. I thought they might only have done it for the sandbox environment.

mdPartnerNL

with sandbox i got the same error as you have.

i use: https://api.tradeshift.com/tradeshift/rest/external

pdj

Thank you - I will contact Tradeshift and hear if they both are upgraded til TLS1.2 or if only the sandbox is upgraded.

pdj

Microsoft has accepted this problem, and it will be fixed in the May CU.

pdj

The problem is fixed in the 2018 May CUs, but you will need to add this line to the CustomSettings.Config:

<add key="SecurityProtocol" value="Tls12"/>