Skip to main content

Setup Windows Authentication with Business Central - On Premise

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:

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>]
   [-SOAPServicesPort <ServicePort>]
   [-ODataServicesPort <ServicePort>]
   [-DeveloperServicesPort <ServicePort>]
   [-SnapshotDebuggerServicesPort <ServicePort>]
   [-DatabaseServer <DatabaseServer>]
   [-DatabaseInstance <DatabaseInstance>]
   [-DatabaseName <DatabaseName>]
   [-Multitenant]
   [-DatabaseCredentials <PSCredential>]
   [-ClientServicesCredentialType <String>]
   [-ServicesCertificateThumbprint <ClientServicesCertificateThumbprint>]
   [-ServiceAccount <ServiceAccount>]
   [-ServiceAccountCredential <PSCredential>]
   [-ServerInstance] <String>
   [-Force]
   [-WhatIf]
   [-Confirm]
   [<CommonParameters>]

Ensure that the CredentialType on NAv Server Instance is set to Windows

2. Creation of NAVWebServerInstance:
You will need to run the New- NAVWebServerInstance Powershell command to create WebServer Instance.


Powershell Command: New-NAVWebServerInstance -Server localhost -ServerInstance UAT -WebServerInstance UAT

At this point, both your Server Instance and Web Server Instances are created. These instances are generally created with default configurations provided in the Business Central installation.
Open the navsettings.json file in C:\inetpub\wwwroot\<WebServerInstanceName>\ path and set Credential Type to Windows, update the Port No, Server, and Server Instance Name.

3. Create a Self-Signed Certificate and bind it with the host:
For the creation of Self Signed Certificate in Business Central, refer to Step 3 at https://www.olisterr.blogspot.com/2020/03/how-to-setup-navuserpassword-with-ssl.html
Also, add NT AUTHORITY\NETWORK SERVICE User through Manage Private Keys.

For binding the certificate in IIS refer to Step 7 at  https://www.olisterr.blogspot.com/2020/03/how-to-setup-navuserpassword-with-ssl.html

4. Restart NAVServerInstance and NAVWebServerInstance:
Restart the NAVServerInstance through Business Central Administration or Powershell.
Restart the Web Server Instance by restarting IIS Service.

When you open the Business Central URL, you will get a pop-up to insert your Windows Credentials
Insert your Windows Credentials to log in

Business Central Dashboard


Conclusion:

I hope this blog helps you quickly setup Business Central through Active Directory Credentials.
If case of any issue feel free to drop a comment or email me at olisterr@outlook.com

Thanks and Cheers!!

Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant 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 Insta

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe

Installing LS Central - POS on local machine

Introduction: In this blog, I'm attempting to capture the LS Central - POS installation process on Local Machine. This blog has nothing to do LS Central - Server Setup for POS. LS Retail / LS Central - On Premise POS Pre- requisites : LS Central Installed on Server SSL Setup on LS Server (https://www.olisterr.tech/2020/03/how-to-setup-navuserpassword-with-ssl.html) LS - POS Installer Business Central - On Premise Installer Demonstration: Once your LS Retail / LS Central POS is setup on the main server. Just prior to Go-Live, you will actually have to install this POS on multiple systems and connect these POS to the main server with LS Retail / LS Central. 0.Preparation: Prior to actually installing Business Central On-Premise Windows Client, you need to make sure that you're able to ping the target with the correct Port number. For this I made use of PS-Ping tool.  PSPing - IP Address: Port If you're unable to PS-Ping the correct IP with Port number, simply check the Advan