Developer forum

Hi Adrian,
I can not get this reproduced. See mine setup below. I am using NAV2018 and its exposed DW web service from the codeunit directly without any connector service involved.
Endpoint authenticaion is using the Ntlm (same as configured in the NAV administration server tool):

Endpoint settings:

Endpoint authentication is set to "ntlm" configured in the first step.
Then in the live integration I have the endpoint selected:

Then I am able to connect and submit products and orders request to the NAV server just fine.
BR, Dmitrij

Could be TLS version problems on your the endpoint vs Dynamicweb.

It could be that the SSL they configured is a specific version that your DW is not configured to run. 

Hi guys,

Thank you for all the details.

First, I would like to understand how I should set it up on our end. In my situation, we need to connect to AX 2012. And I have tried to configure Live integration the same way I did for the past 5 years. No endpoint, just plain settings in the Live integration dialogue. I have also tried it from the TestTool and I got the message mentioned earlier.

From what Dmitrij is saying, I understand that I can define an endpoint instead of the regular settings inside the Live Integration configuration?

Secondly, if there are any limitations in terms of supported versions of TLS, it would be useful to know them in order to specify them to our customer.

Thank you,

Adrian

Hi Adrian,
that is probably because the AX connector maybe not support the https. The NAV connector supports that.
If you are using the AX connector then I've made some code to try the https in the same way as we have for NAV, you can donwload it from here but I am not sure it works
since I have not tested it with the AX on https running. The DW service AX connector config tag should be this:
<add key="BindingType" value="BasicHttpBinding" />
It is also hardcoded to Ntlm in ClientCredentialType, so try to set it to Ntlm in the Ax Admin server settings.

BR, Dmitrij

Hi Dmitrij,

I am afraid it is more complicated than that.

As I have mentioned, these guys are very concerned by security.

They have exposed the HTTP endpoint to AX through a proxy that exposes an https endpoint.

I don't have all details and it seems that even from Postman the request does not go through.

I will suggest your solution, maybe this way they can get rid of the proxy part and expose an https endpoint directly from AX.

Thank you,
Adrian