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

How to configure WS-Security for SOAP Services?



How to use WS-Security instead of Basic Authentication using LDAP and leverage username token profile to authenticate the application user? Any authenticated PRPC operator must not be able to invoke the SOAP Service, which is possible with Basic Authentication.


Perform the following:
  1. In Service Package, clear the Requires-Authentication check box selection.
  2. Navigate to Service SOAP rule > Advanced tab and enable WS-Security option. Specify Security Profile.
  3. Provide a valid username and password in the WS-Security Profile. When SOAP Service was run standalone, by clicking Play button, request envelope and response were generated without any issues.
  4. Create a SOAP Connector in PRPC to test the SOAP Service configured through the above steps or use external tools like SOAP-UI.

Published October 17, 2016 - Updated October 8, 2020

Was this useful?

66% 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