Introduction
Obtain authentication and other information from Microsoft Dynamics 365. This includes OAuth 2.0 client credentials, the tenant ID, grant type, client ID and secret, and scope.
Application Configuration in MSD 365
An application must be created in the Microsoft Entra Admin Center. Follow these steps to create the application:
Navigate to Microsoft Entra Admin Center.
Log in with your Microsoft Admin Account.
Go to Applications > App Registrations.
Click on Create New Registration.
Enter a display name for this application.
Choose the appropriate option to determine who can use this application.
Enter a Redirect URL (optional);
https://portal.ipaas.com/customer/subscription-mgmt/subscriptions/authorization/app(for the returning authentication responses (tokens) after successfully authenticating or signing out users)
You will now receive the Client ID and Tenant ID.
Certificates & Secrets
Click the Certificates & Secrets tab.
Click New Client Secret.
Add a description and set the expiration for the client secret.
Click Add to generate the Client Secret. Save the client secret in a secure location, as it can only be copied once and will not be displayed again.
Return to the App registrations tab and select Overview.
Application Client ID:
opy the Application (client) ID. This is the Client ID you will use installing the integration.
From the App registrations > Overview tab, find and copy Directory (tenant) ID.
Add Permissions in Microsoft Dynamics 365 Business Central
Go to the API permissions then click Add a permission.
On the Request API permissions screen, select Dynamics 365 Business Central.
Select Application permissions and select or add the following permissions:
app_access
AdminCenter.ReadWrite.All
API.ReadWrite.All
Automation.readWrite.All
OAuth 2.0 Client Credentials Grant Configuration
The OAuth 2.0 client credentials grant flow allows a web service (a confidential client) to use its own credentials to authenticate and access another web service. This flow is for applications that need to act on their own behalf, without a user's involvement.
Permissions are granted directly to the application by an administrator.
The application itself is authorized to perform actions since no user is involved in the authentication.
This flow provides an access token valid for 60 minutes. To generate an access token, the following details are required in the iPaaS.com subscription settings:
Tenant ID: The directory (tenant) ID where the application is registered.
Grant Type: Must be statically set to client_credentials.
Client ID: The application (client) ID assigned to your app during registration.
Client Secret: The secret key generated for the application. This value must be saved in a secure location.
Scope: The specific permissions or resources the app is requesting access to.
For our configuration, this must be statically set to
https://api.businesscentral.dynamics.com/.default.
The.defaultscope is used to refer generically to a resource service (API) without specifying individual permissions.
OAuth 2.0 Authorization Code Grant Configuration
The OAuth 2.0 authorization code grant type enables a client application to gain authorized access to protected resources, such as web APIs. This flow involves a user signing into the app to access their data. This flow requires a user-agent (like a web browser) that can be redirected from the authorization server back to your application. A user must sign into your app to access their data.
This flow provides:
An access token valid for 60 minutes.
A refresh token to get new access tokens without requiring the user to re-authorize the application. This allows for seamless subsequent requests.
To configure this grant, you need the following:
Tenant ID: The directory (tenant) ID where the application is registered.
Location: Found in the Microsoft Entra admin center under Identity > Overview > Tenant information.
Client ID: The unique application (client) ID assigned to your app.
Location: Found in the Microsoft Entra admin center under Identity > Overview > Client ID information.
Response Type: Must include code for the authorization code flow. It can also include an id_token or token.
Redirect URL: The URL of your app where authentication responses will be sent.
With this information, you can install the integration.
Integration Configuration for MS Dynamics Basic Authentication
Log in to iPaaS.com based on the environment where you want to configure your application.
Select your company where your MSD 365 Integration exists.
Go to Subscriptions Management and click Search Certified Integration Marketplace & Subscribe.
Click the Microsoft Dynamic 365 Integration title.
Click the Subscribe button.
Enter the Name of the subscription and select a version. It can be set to any relevant and unique subscription name within the company where this subscription is created.
Provide the API URL endpoint for you Microsoft Dynamics 365 instance.
Environment URLs:
Test/Sandbox:
https://api.businesscentral.dynamics.comProduction:
https://api.businesscentral.dynamics.com
Enter the Environment. For example, WEBsB2.
Enter the Tenant ID. For example,
08d1a030-9b1a-491d-a1fe-8fd964a372faEnter the Company Name.
Enter the Tenant ID, the Microsoft directory where the application is registered. You can find this in the Microsoft Entra Admin Center > Identity > Overview >Tenant Information. Copy the value and paste it in.
Set Grant Type to client_credentials.
Enter the Client ID, the unique identifier for your application registered in Microsoft Entra ID. You can find this at Microsoft Entra Admin Center > Identity > Overview > Client ID information.
Initiate the OAuth Flow and Generate the Access Token
Go to the Microsoft Dynamics 365 Subscription that was created earlier.
Click the Authentication icon in the top toolbar.
A new browser window will open, redirecting to a URL containing code, state, and session_state parameters. A success message displays if the code is validated.After the confirmation page is displayed, you may close the window.
Refresh the iPaaS.com subscription page .If successful, the Access Token and Refresh Token will now be populated.
NOTE: If an error occurs, double-check that all settings match the configuration described above. |