Hi, I've been creating an implementation extending Customer Service for Healthcare , and I'm trying to use CDM and Pega locally to get my data, but I'm having problems when I run the Data page D_Contact_List to verify the connectivity.

I'm getting the error Unable to obtain access token for client details in authentication profile configured for connector. Please check the logs for more details. I have checked the logs and I see the following:  

Unable to complete interaction with remote resource: Caught Exception while creating OAuth2 client

Unable to obtain access token for client details in authentication profile configured for connector. Please check the logs for more details

As per Troubleshooting I have gone through every applicable item on the list but I'm still not able to pull the data.

My setup is as follows:

Application Layers:

1. BaseCSHCDEV 

2. BaseCSHC

3. CustomerService-HC-Constellation/PegaKM

I have followed steps in Required setup to prepare the new implementation application which cover most points in the troubleshooting checklist, please see my setup below:

For the toggle:

the screenshot in the documentation suggests to append a "CS" to the name of the app identifier, I have also created an additional Toggle CDM_BaseCSHCDEV to match the application identifier. Does the toggle identifier matters for anything other than the example below?

 For DetermineExtension_Ext

​

The name of the Toggle is referenced here, I have added both the implementation and developer layer. Do we need to enable the toggle on each layer to properly use the common data model in both layers?

For the OAuth 2.0 Client Registration

Pega creates one OOB named as the application id, I have created a new one, following the naming of the Toggle as the troubleshooting page mentions using a Client Registration for Authorization only, the one created OOB is configured to Grant Authorization Code , while this one uses client credentials. I copied the configuration from the OOB CS Application rule but the documentation is not clear, as if the same rule can be reused or is the best practice to create a new registration for CDM uses specifically?

Authentication Profile

The authentication profile with the previously generated client id and secret , the name breaks the naming condition pattern as this one has been set in data transform SetCDMAuthenticationProfile in the field .AuthenticationProfile

From the troubleshooting page, the rest of items I don't think are applicable as I have not started to extend any data transform. I do have an additional table as per Ref Data Tag, the documentation is not clear as if the Tag needs to match/align to something else, so I have the name of the app itself.

I would appreciate more insight to continue troubleshooting on my end, and any additional context for the effects of the configurations above.