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

Introduction: In our previous blogs, we discussed setting NAVUserPassword and Single Sign-On Authentication in Business Central. In this blog, we will be working on setting Windows Authentication in Business Central On-Premise. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://www.olisterr.blogspot.in/2020/03/how-to-setup-single-sign-onsso-for.html https://www.olisterr.blogspot.in/2020/03/how-to-setup-navuserpassword-with-ssl.html Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Instance - Ports and Service Account - Business Central Administration PowerShell Command:  New-NAVServerInstance    -ManagementServicesPort <ServicePort>    [-ClientServicesPort <ServicePort>]    [-SOAPSe

07/10/2020 - Update on Self-Signed Certificate Setup Process for NAV / Business Central  As per my previous post on setting up NAVUserPassword here Reference:  https://community.dynamics.com/nav/b/dynamicsnavcloudfronts/posts/how-to-login-windows-client-and-web-client-using-navuserpassword-authentication-in-microsoft-dynamics-nav If you have created a Certificate using the above PowerShell command and it gives error while starting the NAV / BC Instance with the error as follows: ******************************************************* Server instance: DynamicsNAV100 Tenant:  <ii>The service MicrosoftDynamicsNavServer$DynamicsNAV100 failed to start. This could be caused by a configuration error. Detailed error information: System.ArgumentException: It is likely that certificate 'CN=navision.southeastasia.cloudapp.azure.com' may not have a private key that is capable of key exchange or the process may not have access rights for the private key. Please see inner exception for

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 my previous blog on  How to Setup NavUserPassword with SSL for Microsoft Dynamics Business Central , I have performed all the steps in such a way that it would perfectly fit with this blog to give you Single Sign-On(SSO) based access to Microsoft Dynamics 365 Business Central. Pre- requisites : How to setup NAVUserPassword Authentication Understand how AzureAD Authentication works Microsoft Dynamics 365 Business Central On-Premise Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/authenticating-users-with-azure-active-directory Demonstration: 1. Preparation for SSO: Perform all the steps for NAVUserPassword based authentication. Refer here  How to Setup NavUserPassword with SSL for Microsoft Dynamics Business Central 2. Connect your device to AzureAD: Install Azure AD Module Install Azure AD Module by running the command highlighted After installation of Azure AD Module, in order

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