olisterr.tech | Blog on Dynamics 365 Business Apps, NAV / Business Central, Power Platform and Azure

Introduction: In one of my blog on Setting up OAuth Authentication for Webservices and APIs in Dynamics Business Central, I shared how to setup OAuth Authentication. With Dynamics 365 Business Central releasing version 20, the Webservice Key Authentication has become OBSOLETE and all your integrations are to be moved to OAuth Authentication. There are few more steps in addition to the steps I mentioned in the blog above and those will be seen in the demonstration. Pre- requisites : Microsoft Dynamics 365 Business Central Understanding OAuth Authentication Understanding Azure App Registration Demonstration: 1. Complete all the Azure App Registration : Complete the Azure App Registration process as mentioned in the blog  Setting up OAuth Authentication .  2. Change the Redirect URL in Azure App Registration: Change the Redirect URL in Azure App Registration > Authentication to https://businesscentral.dynamics.com/OAuthLanding.htm 3. Azure Active Directory Application: In Business Cen

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

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,

Introduction: Today, I found something interesting in Business Central. When you open Users > Select User > Web Service Key Field, you will notice that it is either blank, has some value, or has a string of  '*' symbols Pre- requisites : Microsoft Dynamics 365 Business Central Demonstration: 1. When you open a current logged in User: You will notice that the Web Service Key is <BLANK> if not configured. If the Web Service Key is configured then you will be able to find the key. You can triple-click to select the whole key.           Current User 2. When you open a different User from currently logged in User: You will notice that the Web Service for a different User will be '**************************' after version 16.5 and above. Which also means that even if you copy the Web Service Key to the clipboard you will receive the same '****************' character. Earlier this wasn't the case, instead, we were able to simply check the keys for diffe