Question

3
Replies
3101
Views
Karumanchi Sujatha (KarumanchiS)
Appmajix Technologies

Appmajix Technologies
IN
KarumanchiS Member since 2018 1 post
Appmajix Technologies
Posted: March 15, 2018
Last activity: March 26, 2018
Posted: 15 Mar 2018 1:10 EDT
Last activity: 26 Mar 2018 11:17 EDT
Closed

Consuming REST servce from PEGA 7 with HTTP Header parameter

I am not a PEGA developer. But this question is for any PEGA developer/admin. This is about an issue which I noticed recently while trying to integrate my application (using REST service) with PEGA 7.

I created a REST service from my application and hosted it with OAuth 2.0 authentication. PEGA application has to consume my service.

Using any REST testing tool such as Chrome's REST console, APIgee, etc., I was able to test my REST service by just passing the http-header param as [param name: Authorization & param value: OAuth ].

But PEGA had an issue in directly supplying the http-header parameter to test my service from PEGA PRPC application.

My Questions for PEGA developers/Admins are,

  • is it difficult from PEGA to add a header param in http calls
  • On request, PEGA screen was shared with me while a developer attempted to test my service from PEGA. During which I noticed that PEGA did not have any trace logs to capture the exact http request that was generated. Is it true that we could not see the http request (header/body) that was generated from the REST connector tool?

Link to my question on stackoverflow website: I am not a PEGA developer. But this question is for any PEGA developer/admin. This is about an issue which I noticed recently while trying to integrate my application (using REST service) with PEGA 7.

***Updated by moderator: Lochan to add additional context to post***

Data Integration Security
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.