Skip to main content

How Do I - Configure NavUserPassword with Business Central on-prem with Certificate?

Hi Readers,

I used to write this article every year but didn't do it for few versions. 

In this article we will discuss steps to Setup SSL Certificate in Business Central on-prem.

Steps in this article, can be followed with Business Central 21 or higher. I have tested this with Business Central 22. If something changes in Business Central future release, we will write a new article. 

#msdyn365bc, #credentialtype


To start with We will create a Self-Signed Certificate.

  1. Open ISS Manager, Choose Server Certificates.


    2. Create a New Self-Signed Certificate.


    
    3. Copy the Certificate Thumbprint and DNS Name.



    4. Update Service Tier.

  • Set-NAVServerConfiguration -ServerInstance BC220 -KeyName ServicesCertificateThumbprint -KeyValue Thumbprint
  • Set-NAVServerConfiguration -ServerInstance BC220 -KeyName ClientServicesSSLEnabled -KeyValue true #This step is only for version 21 and later.
  • Restart-NAVServerInstance -ServerInstance BC220

** Change Parameter in Bold.

    5. Update Web Server Parameter.

  • Set-NAVWebServerInstanceConfiguration -WebServerInstance BC220 -KeyName DnsIdentity -KeyValue DNSName
  • Set-NAVWebServerInstanceConfiguration -WebServerInstance BC220 -KeyName RequireSsl -KeyValue true
  • Set-NAVWebServerInstanceConfiguration -WebServerInstance BC220 -KeyName ServerHttps -KeyValue true

** Change Parameter in Bold.

    6. Update Certificate permission for Service Account.
  • Open MMC.exe.
  • From File Menu, Select Add/Remove Snap in.
  • Choose Certificate and add and choose Computer Account.
    

  • Expand Personal Node and Select Certificate Folder.
  • Choose Certificate, from all tasks, choose Manage Private Key.


  • Make Sure that Service Account (Service Running with user), have permission to certificate.


  • Bind Certificate with Web Site, Select Website, Choose Binding.
  • Add new binding with https and map certificate.


Hopefully you learned something new in this article. You can also watch following steps below.


Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searchi...

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.