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,
right-click on the Certificate > All Tasks>Manage Private Keys > Add NETWORK SERVICE and allow access to all the users and copy the certificate to Enterprise Trust, Trusted People, Trusted Publisher and Trust Devices folder.
 |
| Change Credential Type and Add Certificate Thumbprint |
5. Change the CredentialsType in navsettings.json files:
This tells Business Central Clients to change the CredentialTypes for the Client.
Goto C:\inetpub\wwwroot\<WEB SERVER INSTANCE>\navsettings.json
 |
| Change Client Service Credential in navsettings.json |
6. Go to Users in Business Central, insert the Password:
 |
| Add Password to Users in Business Central |
7. Binding your Web Server Instance with SSL / Self-Signed Certificate in IIS:
 |
| IIS Bindings for with SSL / Self-Signed Certificate |
Restart the Server Instance in Business Central Administration and Webserver instance in IIS.
Output:
 |
| NAVUserPassword in WebClient |
 |
| Business Central with NAVUserPasswod and accessible all over the world wide web. |
Conclusion:
Importantly, we need to correctly setup SSL Certificate and how to bind with IIS.
In the next blog, I will show how to setup Single Sign-On(SSO) in Microsoft Dynamics Business Central and connect Business Central with Azure AD to login with your Office 365 credentials.
Despite all following these steps if you have issues starting Server Instance then refer to my blog HERE
Hi Olister,
ReplyDeleteHow to apply certificate if we have 4-tier architecture. I completed the installation & configuration as Server1 (SQL), Server2(NST), Server3(IIS,Web) & Server4(RTC Client). All are working well with windows authentication. Now I have to change the authentication to NavUserPassword. For NavUserPassword I need to apply SSL, here I am not sure that how many SSL certificate needed and how to configure?
See this blog describing the installation & configuration
https://docs.microsoft.com/en-us/dynamics-nav/walkthrough--installing-the-microsoft-dynamics-nav-web-server-components-on-three-computers
Thanks,
Manish Sinha
Manish,
ReplyDeleteFor NavUserPassword it is not mandatory to use SSL unless you want to access your webclient over the Internet and not through local connection.
For SSL, you need to make sure that your SSL pings to the URL that you wan to access after which your NAVUserPassword with SSL will work.
Check if you can get NavUserPassword working without SSL in your LocalMachine.
Thanks,
Olister.
Hello,
ReplyDeletei follow thios article and has a uknown error when i will log in to NAV ... error: "An error has occurred" and I can only log out.
Whats this error ?
Kind regards
Same error here on a 17.2 version
ReplyDelete