Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Enabling fails with WS Security profile on Connect-SOAP

SA-10497

Summary



User is facing an issue while enabling Web Service Security in Connect SOAP rule using username and password authentication.
Following are the issues identified with the user's configuration:

*WS Addressing is not selected due to lack of documentation.
*Username and Password which is part of outflow, are specified in the inflow. The webservice is not sending username and password while serving the request.

Error Messages



pySOAPFaultReason :
security.wssecurity.WSSContextImpl.s02: com.ibm.websphere.security.WSSecurityException: Exception org.apache.axis2.AxisFault: CWWSS6500E: There is no caller identity
candidate that can be used to login. ocurred while running action: [email protected]61

pySOAPFault :
<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>security.wssecurity.WSSContextImpl.s02: com.ibm.websphere.security.WSSecurityException: Exception org.apache.axis2.AxisFault: CWWSS6500E: There is no caller identity candidate that can be used to login. ocurred while running action: [email protected]21</faultstring><detail /></soapenv:Fault></soapenv:Body></soapenv:Envelope>


Steps to Reproduce



1.Generate Connect SOAP rule with Connector Meta Data wizard.
2. Enable WS Security by selecting the checkbox.
3. Provide a security profile, selecting username and password in the outflow and username and password in the inflow.



Root Cause



The root cause of this problem is an error/omission in product documentation. When WebService Security (WS Security) is enabled, WS Addressing has to be selected, which is another configuration parameter part of the advanced tab in the connect SOAP rule, which is not specified in the documentation.

Resolution



This issue is resolved through the following local-change:

1. Select WS Addressing option.
2. User is adviced to remove the configuration in the Inflow tab of the security profile.

Published June 24, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us