Skip to main content

NAV 2013 & NAV 2013 R2 - Web Services With Qualified SSL Certificate - Configuration.

Hi all,

As promised in Last post Below are the changes that we need to do while creating certificate for having the SSL Certificate with Qualified Name.


Why Qualified SSL Certificate ?

As in Last post we saw that after configuration of SSL enabled web services, we got an Security Warning about Certificate while accessing the web services on web Browser as shown below -





"The Security Certificate presented by this website was not issued by a trusted certificate authority."

AND

"The Security Certificate presented by this website Issued for a different website's address."

Why We Got Warning Message?

When we try to access a URL which is SSL Enabled then the Certificate should be Generated as machine name to be Qualified.

How to Resolve the Warning Message?

If you remember we used below command to Create the Certificate -

---------------------------------------------------------------------------------------------------------------
makecert -r -pe -n "CN= Nav Test Cert" -b 01/01/2014 -e 01/01/2044 -sv certifiatename.pvk certifiatename.cer
---------------------------------------------------------------------------------------------------------------

For Qualified Name - The Cerficatename Should be Same as the Full Computer Name of Microsoft Dynamics NAV Server.

How to Get the Complete Machine Name?

1. Go to Properties of My Computer.
2. You will see the Full Computer Name as shown below.


Just Replace the Certificate Name in Query as the Full Computer Name shown in Microsoft Dynamics NAV Server. Then Follow all steps as listed in previous article. 

Hope this helps.

Stay tuned.

Regards,
Saurav Dhyani

Comments

  1. Hi Saurav..This is not working as the trust is not enable on the certificate..can we have alternate way ?

    ReplyDelete
    Replies
    1. Hi Lokesh,
      I dont know, i think you can create a ticket in Forums and others will be able to suggest alternate solutions or not.

      Delete

Post a Comment

Popular posts from this blog

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.

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.