Skip to main content

Update to OAuth in Dynamics Business Central v20

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 Central > Search 'Azure Active Directory Application' > Open the Azure Active Directory Application Card.
Use the Application ID from Azure App Registration and paste in the Client ID.  
 Now, go ahead and Grant the Consent using the Adminstration account. This will open the login screen as you get during login, put in the Admin Credentials and you are authenticated to connect.

Conclusion:

It might happen that your OAuth Authentication might authenticate your webservice if you are on BC v19.
However, I have observed this step to be mandatory in BC v20.
I hope this helps and thanks for reading.😄

Comments

  1. I am still facing the issue in postman i got the token successfully but after configuring it in BC i am not able to retrive the data it giving error 401. Unauthorized. kindly suggest.

    ReplyDelete

Post a Comment

Let me know your comments below. I'll try my best to answer your comment

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