Question

REST Service response getting encrypted in Base64 format

<p>the Response of rest service is getting encrypted in Base64 format. This issue is happening only is PRODUCTION env, where SSO authentication is implemented. In all other env it is working fine. We have user POST method.&nbsp;</p>

<p>The Content- Type header parameter is missing in the Response headers. Even when we are explicitly adding the parameter, it is missing in upstream system.&nbsp;</p>

<p>Can anyone tell me if there is any possibility to remove the content type parameter during the response going out of PEGA server?</p>

<p>&nbsp;</p>

<p>&nbsp;</p>

<p>&nbsp;</p>

***Moderator Edit-Vidyaranjan: Updated SR details***

Group Tags

Correct Answer
September 24, 2019 - 3:25am

the issue is resolved. As per the analysis with upstream systems, we found that Dynatrace agent installed on upstream Environment which is adding additional cookies ( dtcookies) while sending request causing response encode to BASE64 format failure from Pega. The Dynatrace cookies injection disabled to PEGA  and it is working now.

Comments

Keep up to date on this post and subscribe to comments

September 7, 2019 - 6:53am

To clarify, what is the acceptable (working) response header Content-Type value versus not-working (Prod) for your upstream system? Are these your own servce-rest or Pega OOTB Pega APIs? Can you elaborate the env difference between working and non-working environments?

September 7, 2019 - 7:30am
Response to KevinZheng_GCS

The Content-Type should be application/json. this is a new REST service created for application. there is no difference between Prod and Pre prod env.

September 7, 2019 - 7:44am
Response to GOURABKETAN

so the difference is the upstream application (clients)? The requirement is different for the prod env from the client side? (Pega is server side)

September 7, 2019 - 7:48am
Response to KevinZheng_GCS

As per upstream system , the Pre Prod and prod is same for them as well. the the request they are sending to PEGA is same for both the envs.

September 7, 2019 - 7:53am

so what exactly is the error? You can turn on debug on the pega side to compare the differences btw working/non-working cases: 

com.pega.pegarules.integration.engine.internal.services.http.HttpService

September 24, 2019 - 3:25am

the issue is resolved. As per the analysis with upstream systems, we found that Dynatrace agent installed on upstream Environment which is adding additional cookies ( dtcookies) while sending request causing response encode to BASE64 format failure from Pega. The Dynatrace cookies injection disabled to PEGA  and it is working now.