Skip to main content

NAV 2013 R2 Windows Client & Web Client with NavUserPassword - Configuring the Credential Type for Microsoft Dynamics NAV Server.

Hi all,

This is third post in this series. Please make sure that you have read all the Previous post before you start reading this post.

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

Let's move ahead from where we left yesterday.

31. We need a user that we will use to Run the Windows and web client.

32. Let's Open windows client and create a user.

33. Provide a UserName (TESTNAVUSER), assign Role(For me its SUPER) and Provide a Password (TestNAV123).

34. Click OK, it will give you a warning. Click YES.

Changes in Service Tier -

35. Close windows client.

36. Open Microsoft Dynamics NAV 2013 R2 Administration.

37. Create a New Service for Testing (Say TestNAVUSerName).

For New Services i.e TestNAVUSerName following Port Numbers are used (We will require these Port During Configuration of Clients)-

Management Services port - 10045
Client Services Port - 10046
SOAP Services Port - 10047
OData Services Port - 10048

* We are doing this so that our existing setup should work in case there is an issue with what we are trying.

38. Edit the Service and change -

a) Credential Type to NavUserPassword.
b) Certificate Thumbprint as shown at the end of Post 2.

39. Save and Restart the Service.

40. It should be up and Running.

In Next Post we will see what need to be changed in client (RTC and Web) for using NAVUSerPassword.

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.