Eric's Tech Blog

1/13/20 - This apparently only applies to NAV.  See note at the end for connecting to Business Central It took me a little while to nail down authenticating to a Dynamics NAV OData web service with Postman.  Fiddler does it quite easily but I suspect it is a little more intelligent while Postman requires the correct settings for everything. First, in NAV you need to have NTLM authentication enabled.  I have found this is required any time you want to use the web services with anything other than .NET (and even then...). Now, with NTLM enabled, you might think the authentication is NTLM but you'd be wrong.  It's Digest.  There are two flavors of Digest: MD5 and MD5-sess.  By default, Postman will come up with MD5.  I discovered it was supposed to be MD5-sess by using Chrome's developer console.  With this console open, make the GET request and you can see all of the data being exchanged. Within the Authorization header, toward the end, you will see an algorithm setting

While .NET Core is intended to be run as a standalone application, I enjoy the convenience of running it through IIS on client systems.  This is especially nice since the applications I develop are microservices meant to augment the functionality of the Dynamics Business Central ERP system.  Often I will piggyback these on the already open port for the web client thus bypassing the need to involve IT in the process. All of the documentation I've seen shows this being a much more complicated process than I have found it to be.  For my own memory and for the edification of the rest of the world (if anyone else reads this), here are the steps I have found to be needed to deploy a .NET Core application on IIS as of 2.2. Download the latest .NET Core Hosting Bundle  and install it. Restart IIS using IISRESET from an elevated command prompt (or just restart the server if you feel like it). Take the published version of your application produced by Visual Studio and copy it ont