REST Connector: Incorrect pyStatusValue
In Pega 7.1.4, when user is running a data page to execute the Connect REST rule with an incorrect credential, the pyStatusValue returned is "Fail: Authentication parameters incorrect" as expected. In 7.1.6, the pyStatusValue returned is "Fail:InternalReason"
Steps to Reproduce
Call the Connect REST rule with an invalid login credentials
Some REST APIs return important information in the body or headers, such as "your password has expired," when there is a 401 response code. Starting in PRPC 7.1.6, by default, we no longer avoid consuming the body and headers in order to provide details about the failure.
Avoid consuming the body and headers when there is a 401 response code by creating the following Dynamic System Settings.
Owning Ruleset: "Pega-IntegrationEngine"
0% found this useful