Question
First Tech Federal Credit Union
US
Last activity: 13 Apr 2016 15:03 EDT
GET Request configuration
Hi. I tried to configure a GET request for a Connect REST service on Pega but it fails the connectivity test. I tried to configure the same details on Postman (to test GET request) and it works fine there. On running the connectivity test on pega, it shows connection error while executing GET request. Anybody knows what additional configuration is needed to fix this? Thanks.
Pega Version - 7.2 Personal Edition
Error - Attached 
I have run the same on Postman as well to check the output and it came out fine.
Yes it is an HTTPS URL.
Accepted Solution
Pegasystems Inc.
CA
I see what the problem is. What you are trying is test connectivity. The main intent of test connectivity is to check if the endpoint is reachable or not. The results of test connectivity may not be the exact replica of those from a runtime invocation of connector. I'm sure if you test the runtime execution of the same connector using a data page or a connect activity, you will see the expected result.
However, I do see a bug in test connectivity. We seem to consider "Constant" type resource path parameters and query string parameters for test connectivity but not "Constant" type headers. Had we considered "Constant" headers, test connectivity with your configuration would have worked fine. You could raise an SR for us to fix this. But as I said, your runtime should work fine.
Pegasystems Inc.
US
Please update your post so that your issue can be diagnosed further:
- What Pega version are you using?
- What is the text of the error you are seeing?
- Is the service you are connecting to a secure service (HTTPS)?.
Pegasystems Inc.
CA
HTTP error code 401 seems to indicate an authorization/authentication problem. Does your service expect credentials of some sort to be passed in the request?
First Tech Federal Credit Union
US
Hi Praneeth,
I have passed the bearer token in the header. That should be enough as Postman is able to execute it without any issues. I am attaching a snapshot from Postman just to show how it is working fine on Postman. On applying the same configuration on pega, it is not working.
First Tech Federal Credit Union
US
I tried to run the same configuration on Postman and it worked fine. I am attaching the snapshot from Postman below.
I did the same configuration on Pega as well and it didn't work. Attached is the Service and Method configuration followed by the Test Connectivity results.
I tried to run the same configuration on Postman and it worked fine. I am attaching the snapshot from Postman below.
I did the same configuration on Pega as well and it didn't work. Attached is the Service and Method configuration followed by the Test Connectivity results.
I hope this helps.
Accepted Solution
Pegasystems Inc.
CA
I see what the problem is. What you are trying is test connectivity. The main intent of test connectivity is to check if the endpoint is reachable or not. The results of test connectivity may not be the exact replica of those from a runtime invocation of connector. I'm sure if you test the runtime execution of the same connector using a data page or a connect activity, you will see the expected result.
However, I do see a bug in test connectivity. We seem to consider "Constant" type resource path parameters and query string parameters for test connectivity but not "Constant" type headers. Had we considered "Constant" headers, test connectivity with your configuration would have worked fine. You could raise an SR for us to fix this. But as I said, your runtime should work fine.
First Tech Federal Credit Union
US
Thank you for your help Praneeth. I will use this in an activity and verify it as well and come back with results.
First Tech Federal Credit Union
US
Thanks Praneeth. I used it on an activity and it worked fine. As you mentioned an SR would be required to fix the issue which was pointed out by you.