Developer forum

Forum » Integration » DynamicwebConnectorService NAV DLL fails quietly when the config file doesn't contain username

DynamicwebConnectorService NAV DLL fails quietly when the config file doesn't contain username

E-mail notifications
Jonas Krarup Dam
Reply
Posted on 12/09/2022 12:52:33

See title. 
When using the NAV endpoint connector, if the config file is set to use NTLM or Windows authentication and the config file doesn't contain a "UserName" node, the request is just returned, making it sort of look like the request is working, but with no request being sent to NAV. 
can you please make either fail more loudly, or change it to not require the username node to send the request to NAV? 

Thanks :-) 

/Jonas


Replies

 
Shiwanka Chathuranga Dynamicweb Employee
Shiwanka Chathuranga
Posted on 19/09/2022 13:30:17
Reply

I am not sure is this  a quetion or bug report.

Because DW connector service if you use NTLM authentication method Domain,UserName and Password is required. 

This is NAV Connector properties 

  <NavConnector>
    <add key="UserName" value="" />
    <add key="Password" value="" />
    <add key="Domain" value="" />
    <add key="NavEndpoint" value="" />
    <!-- Set IgnoreCertificateWarnings to true for https endpoints using self-signed or untrusted certificates. Useful for testing. Should be avoided in production. -->
    <add key="IgnoreCertificateWarnings" value="True" />
    <!-- Valid options for ClientCredentialType are: Default, Ntlm, Windows, Basic -->
    <add key="ClientCredentialType" value="Default" />
  </NavConnector>

 
Jonas Krarup Dam
Posted on 19/09/2022 13:42:51
Reply

they are required, but they are not used - the credentials for the user that runs the service are used. 

there is no reason why they are required, and if they are left out when using NTLM, it fails (without giving any indication, but just returning the request XML) - that's what I'm trying to avoid :-) 

 
Dmitriy Benyuk Dynamicweb Employee
Dmitriy Benyuk
Posted on 20/09/2022 21:06:26
Reply
This post has been marked as an answer

Hi Jonas,
it is fixed in the new connector service version 2.1.0 which is now available on the doc site.
BR, Dmitrij

Votes for this answer: 1
 
Jonas Krarup Dam
Posted on 21/09/2022 14:23:46
Reply

Hey Dmitriy,
Great, thank you :-) 

 

/Jonas

 

You must be logged in to post in the forum