Skip to main content


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

Authenticating with basic or NTLM authentication

Updated on November 23, 2022

Configure basic or NTLM authentication to use these methods to send data records to and from your application.

  1. In the Authentication section, select the type of authentication to use to connect to the system of record.
    • None – authentication is not required.
    • Basic – use basic HTTP authentication credentials.
      1. In the User name field, enter a valid user name.
      2. Click Set password.
      3. Enter a password for the user name that you entered.
      4. Click Submit.
      5. In the Realm field, enter the realm of the user account on the server to which you are connecting.
      6. In the Host name field, enter the host name of the server to which the request is being sent.
      7. Optional: To receive a basic authentication request before the server gives an unauthorized response, select Preemptive authentication. Selecting this check box reduces connection overhead.
    • NTLM – to use NT LAN Manager credentials.
      1. In the User name field, enter a valid user name.
      2. Click Set password.
      3. Enter a valid password for the user name that you entered.
      4. Click Submit.
      5. In the Domain field, enter the domain of the user account that you provide in the User name field.
      6. In the Host Name field, enter the host name of the server to which the request is being sent.
  2. Click Initialize call to request data from the REST service and display the response.
    Note: For more information about authentication profiles, see Authentication profiles
What to do next: Map fields from the request to the data view. For more information, see Mapping fields.

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