Options

nav2009 HTTP request was forbidden authentication negotiate

JamesWilcaJamesWilca Member Posts: 4
edited 2015-07-15 in NAV Three Tier
Hi,

I'm new to nav. I have a dynamics web services installed, but for some reason it refuses to negotiate authentication.
Are there other config settings besides ClientCredentialType?

CustomSettings.config
<add key="ClientCredentialType" value="Windows"></add>


A message sent to adapter "WCF-Custom" on send port "Snd_DynamicSentToConsumer" with URI "http://server:7099/DynamicsNAV/WS/APP/Codeunit/ProjectWebservice&quot; is suspended.
Error details: System.ServiceModel.Security.MessageSecurityException: The HTTP request was forbidden with client authentication scheme 'Negotiate'. ---> System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

Comments

  • Options
    MarijnMarijn Member Posts: 69
    You could try setting ServicesUseNTLMAuthentication to true. I am not sure, but I remember doing this in a 2009 webservice situation.
  • Options
    JamesWilcaJamesWilca Member Posts: 4
    I have a server where it works with ServicesUseNTLMAuthentication set to false.

    If you install IIS or not on the navision webservice server, does this change anything?
  • Options
    JamesWilcaJamesWilca Member Posts: 4
    If you see a 401 is because it negotiates NTLM fallback instead of Kerberos.

    In other words SPN or delegate issues.

    In this case the sender account did not delegate to the http/navision server in AD.
Sign In or Register to comment.