agilio | 2021-03-30 20:22:40 UTC | #1
Why does the integration credentials need a User name and Password plus an application ID. https://help.mypurecloud.com/articles/add-a-data-actions-integration/
You register the integration in Azure https://help.mypurecloud.com/articles/register-the-integration-in-azure-active-directory/
I’ve never seen the scenario where we need both an app user and a non-interactive user login The username/password should be able to facilitate data pulls from Dynamics as a D365 user with an appropriate security role. What purpose does Application Id serve?
Jason_Mathison | 2021-03-16 19:16:59 UTC | #2
Hi agilio,
When the Dynamics data actions log in to acquire an OAuth token, the application Id is one of the required fields we have to provide.
--Jason
agilio | 2021-03-16 19:27:08 UTC | #3
Current but when you add the integration in Genesys CLoud it requires Enter the following information:
- Username : Your Microsoft Dynamics 365 login ID.The user must be able to access any data that you want to make available to the Microsoft Dynamics 365 data action integration.
- Password : Password for your Microsoft Dynamics 365 login ID.
- Root Organization Web Address : The URL of your Microsoft Dynamics 365 organization, for example, https://contoso.crm.dynamics.com.
- Application ID : The ID for your Microsoft Dynamics 365 organization.The application ID is created through the application registration in Azure Active Directory. For more information, see Register the integration.
Where does that doc state you need a User?
Jason_Mathison | 2021-03-16 20:31:53 UTC | #4
I checked in the code, the Dynamics data action integration uses all 4 fields in order to get an OAuth token.
Where does that doc state you need a User?
Which documentation are you referring to?
--Jason
agilio | 2021-03-17 12:52:28 UTC | #5
The information I pasted in the previous post is from this link https://help.mypurecloud.com/articles/add-a-data-actions-integration/
It references The User."Your Microsoft Dynamics 365 login ID.The user must be able to access any data that you want to make available to the Microsoft Dynamics 365 data action integration.
agilio | 2021-03-17 14:52:33 UTC | #6
As we understand it, this is how data can be accessed that lives in Dynamics.
Tenant ID in conjunction with Client ID and Secret provides an Access Token for the Application defined in Azure AD. Using the Access token to make calls to Dynamics to perform data operations (as long as the application user is created in Dynamics with the Application ID and has been provided a Dynamics Security role. This provides full functionality from a data access perspective.
The other option is to use a named user (Service Account) within Dynamics with a Dynamics Security role applied to it. This has the same effect and is equivalent to the previous option.
The question that we are asking, is why do we need both options when configuring Genesys when only one will do from a Data Access perspective.
system | 2021-04-17 15:01:39 UTC | #7
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 10291