Skip to main content

Expose Web Service using SSL in Business Central On-Premise

Introduction:

I had a requirement where the Web Services / APIs in NAV and Business Central On-premise needed to be exposed outside the VM to be consumed by third-party applications.
Also, this blog is a continuation of my previous blogs on NAVUserPassword and Single Sign On(SSO) 
In this blog, let us see how to expose the Webservice / API URLs outside the server and consume them.

Pre-requisites:

  • Microsoft Dynamics Business Central On-premise
  • Static IP assigned to the Server
  • DNS configured with SSL or Self-signed certificate.

Demonstration:

1. Changes to Business Central On-Premise / NAV Administration Console: Inside the Administration Console, you need to make sure that either you Business Central already has a way to be authenticated with the DNS link that you have provided. You can refer to my blogs  NAVUserPassword and Single Sign On(SSO) for this

After that make sure you enable SSL and change the Base URL to '<https://YourDomain:Port/ServerInstance>'. Also, make sure to allow the Inbound and Outbound from the Firewall settings as well.

Changes to Administration Console


2. Changes to Base URL in Web Services:
After you have restarted the Server Instance and login to Business Central and navigate to Web Services, you will notice that there is a change to the URL inside the ODATA and SOAP URLs.

Change to Base URL in ODATA and SOAP URLs


3. Calling the Web Service through the browser inside the server:
Simply creating a GET request and providing the credentials, you will also be able to call the ODATA URL and exchange data from inside the server.

Calling the ODATA URL from inside the Server / VM


4. Calling the Web Service through the browser outside the server:
Similarly, a final test to confirm that these URLs are accessible outside the VMs as well.
Calling the ODATA URL from outside browsers

Conclusion:

I deliberately have written this blog because, whenever there are any issues configuring such requirements the most common solution available are done is using costly integration solutions because they have an On-Premise Agent which helps in seamless integration.
I want to make these web services / APIs accessible anywhere over the internet and can be integrated using a custom solution or apps.

I hope this blog helps in documenting the steps for such a process as well.

Thanks for reading.





Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Setting up OAuth Authentication for Business Central Web Services / APIs

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr

How to Upgrade Data from Microsoft Dynamics NAV to Microsoft Dynamics Business Central On Premise - Part 2

 Introduction: Now that the first step of the problem preprocessing of the NAV Database to make it ready to be migrated to BC is done(refer Part 1 ), we can now proceed further with connecting the database in Business Central On-Premise. Pre- requisites : Microsoft Dynamics 365 Business Central Microsoft Dynamics for NAV Microsoft SQL Server Management Studio (SSMS) Powershell ISE Understand NAV to BC Upgrade Considerations -  Click here Understand Upgrade Path -  Click here Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-considerations#online https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-paths https://www.sauravdhyani.com/2018/10/msdyn365bc-data-upgrade-to-microsoft.html https://olisterr.blogspot.com/2022/03/how-to-upgrade-data-from-microsoft.html https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-permissions Demonstration: 1. Install Business