Question4Replies1405Views RAVITEJAP8127 Member since 2015 1 post TATA Consultancy Services Ltd Posted: 2 years agoLast activity: 2 years ago Closed Solved HTTP 403 Error in REST and SOAP connectorsWhen trying to create and test any connector rule, say Connect-SOAP or Connect-REST, a HTTP 403 error comes up.pyStatusVal - Fail: Unexpected HTTP 403 Response code pyStatusMsg - the HTTP response code of 403 indicated a client error. The response data may contain a reason. We get the same error when we try to run OOTB Pega API REST services using connect-REST.Strangely these services run and work standalone as well as when invoked from SOAP UI.Even using the Connect-SOAP wizard, in the very first step of configuring the WSDL source, this fails with same HTTP 403 error.Same is the case for Connect-REST wizard when testing connectivity.On further investigation, we could see the following information on the error : Code:403The response data was not recognized as JSON or XML and cannot be saved. Response Data : Seeing a similar response no matter what the type of Connector it is.Kindly help in resolving this issue. Pega Platform 7.3.1Server : JBoss Pega Platform Low-Code App Development Data Integration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! 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. Posted: 2 years agoGayatri incessant replied to RAVITEJAP8127HI, This link might help you. Posted: 2 years agoAbhinav7 PEGA replied to RAVITEJAP8127Hi, As per the pyStatusMsg property there is issue in response data.Could you please share sample request and response data.Webservice is sending response in which format? Thanks, Abhinav Posted: 2 years agoRAVITEJAP8127 TATA Consultancy Services Ltd replied to Abhinav7Web service is configured to respond with json, which I am very well seeing when testing using SOAP UI. Connector to OOTB Pega API services are also failing. So I don't think that response might be the issue. The same Pega API is working using SOAP UI as well. Accepted Solution Posted: 2 years agoRAVITEJAP8127 TATA Consultancy Services Ltd replied to RAVITEJAP8127Issue Resolved. Below is the resolution: The response hash we were getting is Base64 encoded. We decoded it found it that Jboss was configured with a proxy setting. <system-properties> <property name="http.proxyHost" value="XX.XXX.XXX.XXX"/> <property name="http.proxyPort" value="XXXX"/> <property name="jboss.as.management.blocking.timeout" value="3000"/> </system-properties> So we added a new non proxy setting with the url of our environment. <property name="http.nonProxyHosts" value="localhost, XX.XXX.X.XXX"/> Now the connectivity works fine.