Question
Accenture
IN
Last activity: 24 Sep 2019 3:26 EDT
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. </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. </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> </p>
<p> </p>
<p> </p>
***Moderator Edit-Vidyaranjan: Updated SR details***
Accepted Solution
Accenture
IN
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.
Pegasystems Inc.
US
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?
Pegasystems Inc.
US
so the difference is the upstream application (clients)? The requirement is different for the prod env from the client side? (Pega is server side)
Pegasystems Inc.
US
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
Accepted Solution
Accenture
IN
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.