olisterr.tech | Blog on Dynamics 365 Business Apps, NAV / Business Central, Power Platform and Azure

Introduction: I had a requirement where the Web Services / APIs in NAV and Business Central On-premise needed to be exposed outside the VM to be consumed by third-party applications. Also, this blog is a continuation of my previous blogs on NAVUserPassword and Single Sign On(SSO)   In this blog, let us see how to expose the Webservice / API URLs outside the server and consume them. Pre- requisites : Microsoft Dynamics Business Central On-premise Static IP assigned to the Server DNS configured with SSL or Self-signed certificate. Demonstration: 1. Changes to Business Central On-Premise / NAV Administration Console: Inside the Administration Console, you need to make sure that either you Business Central already has a way to be authenticated with the DNS link that you have provided. You can refer to my blogs   NAVUserPassword  and  Single Sign On(SSO)  for this After that make sure you enable SSL and change the Base URL to '<https://YourDomain:Port/ServerInstance>'. Also,

Introduction: In this blog, I'm attempting to setup basic authentication like NavUserPassword for Business Central On-Premise. NavUserPassword is an authentication system, where each user have their own UserID and password which is configured inside Business Central itself. Pre- requisites : Microsoft Dynamics 365 Business Central On-Premise Domain for your VM Understanding of Credential Types in Business Central Demonstration: 1. Setup DNS in Azure VM: Go to your VM inside Azure to configure DNS. Click on Configure Put the URL as you need. 2.  Create a Webserver Instance for Business Central: New-NAVWebServerInstance to create a Web Server Instance Adding Web Server Instance with the name LS 3. Create a Self Signed Certificate or get an SSL from Domain provider: Run the PowerShell script to create a self signed certificate New Self-Signed Certificate New Self-Signed Certificate created After creation/installation of Certificate, righ