Test Connectivity for REST-Connect Rule - Getting 401 Error
Hello,
I am getting the below error while doing a test connectivity in Connect-REST rule. We are using a HTTP endpoint url with basic authentication and able to receive response using SOAP UI.
The password contains a special character. I am not sure if it is causing an issue?
I am not sure why 401 error is receive after the System is able to connect to the removed server (please see attached screenshot). Any inputs will be helpful.
Note1: I have tried with checking and unchecking the preemptive authentication checkbox in the Auth Profile rule
Note2: I have set the logger name to "Rule_Obj_Activity.pyInvokeRESTConnector.Rule_Connect_REST.Action" and the level to DEBUG - But could not find any information in the log files.
PRPC Version - 7.2.1
Pegasystems Inc.
US
Hello Anuraag,
You can add DEBUG for some other classes related to REST based on their availability in your version as follows,
- com.pega.pegarules.integration.internal.ServiceHelper
- com.pega.pegarules.integration.internal.util.SOAPUtils
- com.pega.pegarules.integration.engine.internal.services.soap.*
- com.pega.pegarules.integration.engine.internal.util.SOAPUtils
- com.pega.pegarules.integration.engine.internal.ServiceHelper
Hope this classes might log some information related to your issue.
Regards
Mahesh
Pegasystems Inc.
US
Please post the version of Pega you're using as well as what character the "special character" is.
This could help us diagnose your issue.
Goldman Sachs
US
Hi, We are using Pega 7.2.1
The special charactar in password is '*'. We have tried changing it to '@' but did not get the desired result.
Accepted Solution
Pegasystems Inc.
US
Based on my review of the "pyTestConnectivity" Activity record for Rule-Connect-REST in version 7.2.1, it appears that the code does not attempt to use the credentials at all, which would explain the behavior.
If you are comfortable modifying this activity, you could try copying the relevant code from step number 4 of the "pyInvokeRESTConnector" Activity record into step number 6 of the "pyTestConnectivity" Activity record.
It is worth noting is that newer versions of Pega such as Pega 7.3 come with a completely re-imagined version of the of pyTestConnectivity Activity, which does not have the problem you are experiencing because it takes advantage of the same runtime code as is used by "pyInvokeRESTConnector," therefore supporting Authentication mechanisms such as Basic Authentication and OAuth when you click the Test Connectivity button.