Skip to main content

NAV 2013 R2 Windows Client & Web Client with NavUserPassword - Create a Security Certificate.

Hi all,

This is first post in this series. All the post related to this series can be found in Introduction Post.

This post will focus on creating the files which are required.

We require to create the certificate , Key and Revocation List which will be used in next post.

Create a Security Certificate.
- Certificate. (.pfx)
- Certificate Key. (.pvk)
- Certification Revocation List. (.crl)

Pre-Requisites -
1. MMC.exe.
2. makecert.exe utility (installed with Microsoft Visual Studio).

To Store all the files which are required i will create a folder in my D Drive called Test Certificate.

Steps -

1. Open Visual Studio Command Prompt as administrator.

2. At the command prompt, locate the temporary directory.

Commands to locate -
 Cd D:\Test Certificate


3. Type Following Command -

makecert -n "CN=NAV2013R2" -r -sv NAV2013R2.pvk NAV2013R2.cer

4. When you are prompted, enter a password. You need this password to create the service certificate.

5. I am using Password as testing.

6. You will find certificate file and private key are saved in your folder.


7. we now create a certificate revocation list for the root certification authority. A certificate revocation list is required because WCF applications check the revocation list when validating certificates.

8. Type Following Command to Create a revocation List (in same window of Visual Studio)-

makecert -crl -n "CN=NAV2013R2" -r -sv NAV2013R2.pvk NAV2013R2.crl

9. Enter same Password when prompted (in my case password is testing).

10. If you check your folder now you will have all the necessary files that are required.

In Next Post we will see how to install these certificates.

Saurav Dhyani


Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.