Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring the authentication for data sources in SOAP integration

Updated on April 6, 2022

You can configure the authentication for one or all the data sources that are created from the operations that you select for your SOAP integration.

  1. To configure the authentication for each data source by selecting an existing authentication profile for the corresponding operation, keep the Use a single Authentication Profile for all Data Sources check box cleared.
  2. To specify or create a common authentication profile for all the data sources select the Use a single Authentication Profile for all Data Sources check box and perform one of the following actions:
    • To choose an existing authentication profile, select Use Existing and enter the profile name.
    • Select Define New to create a new authentication profile and select an authentication scheme:
      Basic authentication scheme
      Requires a user name, a password, a realm name, and a host name. If the external service requires preemptive authentication, you can enable preemptive authentication by selecting the corresponding check box
      NTLM authentication scheme
      Requires a user name, a password, a domain name, and a host name.
  3. If you selected Basic in step 2, to receive a basic authentication request before the server gives an unauthorized response, select Preemptive authentication.
What to do next: Use the authentication profile or profiles for the data sources by clicking Submit and continue with step 4 of Selecting operations for SOAP integration.

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us