Support Article
Connect-SOAP does not work with OAuth 2.0 provider
Summary
Connect-SOAP does not work with OAuth 2.0 provider. However, this works for Connect-REST.
Error Messages
401 Unauthorized
[fault (self-tuning)'] [TABTHREAD1] [ ] [G2GDCM:01.01.01] (internal.mgmt.Executable) ERROR casemanagement-knsit.systems.private|127.0.0.1|Rule-Connect-SOAP.VM-Int-Fusion-UnbillTransac-GetUnbilledTransactio
nDetail.GetUnbilledTransactionDetail - Exception
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_73d14ae0f7fa44255a8cca57e7408a68.step15_circum0(ra_action_invokea
xis2_73d14ae0f7fa44255a8cca57e7408a68.java:3827) ~[?:?]
Caused by: com.pega.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
On the logs, there are no Headers set for the Request,
[fault (self-tuning)'] [TABTHREAD1] [ ] [G2GDCM:01.01.01] (nvoke.Rule_Connect_SOAP.Action) DEBUG casemanagement-knsit.systems.private|127.0.0.1 - Running step 1_circum0
[fault (self-tuning)'] [TABTHREAD1] [ ] [G2GDCM:01.01.01] (nvoke.Rule_Connect_SOAP.Action) DEBUG casemanagement-knsit.systems.private|127.0.0.1 - Invoked in execution mode
[fault (self-tuning)'] [TABTHREAD1] [ ] [G2GDCM:01.01.01] (nvoke.Rule_Connect_SOAP.Action) DEBUG casemanagement-knsit.systems.private|127.0.0.1 - Running step 2_circum0
[fault (self-tuning)'] [TABTHREAD1] [ ] [G2GDCM:01.01.01] (nvoke.Rule_Connect_SOAP.Action) DEBUG casemanagement-knsit.systems.private|127.0.0.1 - Running step 3_circum0
[fault (self-tuning)'] [TABTHREAD1] [ ] [G2GDCM:01.01.01] (nvoke.Rule_Connect_SOAP.Action) DEBUG casemanagement-knsit.systems.private|127.0.0.1 - Running step 4_circum0
[fault (self-tuning)'] [TABTHREAD1] [ ] [G2GDCM:01.01.01] (nvoke.Rule_Connect_SOAP.Action) INFO casemanagement-knsit.systems.private|127.0.0.1 - Starting remote service invocation...
[fault (self-tuning)'] [TABTHREAD1] [ ] [G2GDCM:01.01.01] (nvoke.Rule_Connect_SOAP.Action) DEBUG casemanagement-knsit.systems.private|127.0.0.1 - Running step 5_circum0
[fault (self-tuning)'] [TABTHREAD1] [ ] [G2GDCM:01.01.01] (nvoke.Rule_Connect_SOAP.Action) DEBUG casemanagement-knsit.systems.private|127.0.0.1 - Running step 6_circum0
[fault (self-tuning)'] [TABTHREAD1] [ ] [G2GDCM:01.01.01] (nvoke.Rule_Connect_SOAP.Action) DEBUG casemanagement-knsit.systems.private|127.0.0.1 - Headers: {}
.....
.....
[fault (self-tuning)'] [TABTHREAD1] [ ] [G2GDCM:01.01.01] (internal.mgmt.Executable) ERROR casemanagement-knsit.systems.private|127.0.0.1|Rule-Connect-SOAP.VM-Int-Fusion-UnbillTransac-GetUnbilledTransactionDetail.GetUnbilledTransactionDetail - Exception
com.pega.pegarules.pub.PRRuntimeException: OAuth authentication headers missed in the request.
at com.pegarules.generated.activity.ra_action_invokeaxis2_350f16bcd1d7119aa7f846b7b5fdf70e.step7_circum0(ra_action_invokeaxis2_350f16bcd1d7119aa7f846b7b5fdf70e.java:1693) ~[?:?]
at com.pegarules.generated.activity.ra_action_invokeaxis2_350f16bcd1d7119aa7f846b7b5fdf70e.perform(ra_action_invokeaxis2_350f16bcd1d7119aa7f846b7b5fdf70e.java:173) ~[?:?]
Steps to Reproduce
Invoke any Connect-SOAP instance that is configured to use OAUTH 2.0.
Root Cause
The user cannot map the HTTP headers from the Connect SOAP Rule form. The headers mentioned in the Connect SOAP Rule form are the SOAP headers.
Resolution
An enhancement request, FDBK-67596, is created for consideration by Pega Product Management.
Published April 11, 2020 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.