Skip to main content


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

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.

Configuring a Basic authentication profile

Updated on July 1, 2021

Configure a basic authentication profile so that messages sent to and from your application use basic HTTP authentication credentials.

Before you begin: You must complete the following task before you can configure an authentication profile: Creating an authentication profile.
  1. Open an authentication profile from the navigation panel by clicking RecordsSecurityAuthentication Profile and selecting a basic profile from the instance list.
  2. In the User name field, enter a valid user name for the scheme. The default property for this field is pyUserName.
    This field also supports the Global Resource Settings syntax ( =PageName.PropertyName ).
  3. Click Set password, enter a password that is valid for the user name you provided, and then click Submit. The default property for this field is pyPassword.
    This field also supports the Global Resource Settings syntax ( =PageName.PropertyName ).
  4. In the Realm field, enter the realm of the user account on the server to which you are connecting.
  5. In the Host Name field, enter the host name of the server to which the request is being sent.
  6. Select the Preemptive authentication check box to have the system send the basic authentication request before the server gives an unauthorized response.
    Selecting this check box reduces the overhead of making the connection.
  7. Click Save.

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