Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Anandh Palanisamy (Anandh Palanisamy)
Ford Motor Company

Ford Motor Company
US
Anandh Palanisamy Member since 2013 62 posts
Ford Motor Company
Posted: Nov 13, 2018
Last activity: Mar 16, 2022
Posted: 13 Nov 2018 23:07 EST
Last activity: 16 Mar 2022 6:05 EDT
Closed

Connect SOAP Authentication using OAuth2.0

Hi,

Did anyone connected external system using OAuth2.0 in connect SOAP.

We have mentioned authentication profile in connect rule, when we invoke the service getting below error.

Caused by: com.pega.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized

Did anyone faced this issue? What are rule need to update when you using OAuth2.0 in the connect rule?

Regards,

Anandh

***Moderator Edit-Vidyaranjan: Updated Platform Capability***

 

To see attachments, please log in.
Data Integration
Support Case Parallel

  • Chanthos Selvaraj Ehab Alhourani
Posted: 5 years ago
Posted: 30 Aug 2019 8:33 EDT
Jerome Recker (Jerome@quavo)
375008155608
Lead System Architect
375008155608
US

Will this be changed in future versions of PRPC?  Are there any local changes that can be made so that this works out of box by simply applying the authentication profile to the connect-soap rule?  Can you provide any documentation about this, or explain the reason that this is not supported?

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice