Requests

The Request section is used to create additional HTTP headers or modify existing headers the agent sends when running a test. You can also set up HTTP Authentication in this section.

Note that Request settings are not applicable to all test types, so whether you see the Request section will depend on which type of test you are configuring. All options will be displayed if you are configuring them at the Product or Folder level.

Configuring Request Settings

At the Folder or Test level, Navigate to the Request section and switch the inherited setting to override. This section is already expanded at the Product level. If you wish to use settings from the Parent Folder or Product and additional settings at this level, click the ellipsis and select "Copy Parent." (Passwords cannot be copied and must be manually entered.)

Adding Usernames and Passwords

You can add User Names and Passwords at the Product, Folder or Test level in order to test password-protected resources, such as webpages or servers. Catchpoint supports three standard types of HTTP authentication: Basic, Digest, and NTLM. The Login option enables you to pass the username and password values via macros to your transaction script for application authentication.

Add Credentials from the Library

1. Click + Add User Name and Password
2. Choose Select from Library
3. Select the desired credential from the list
4. Click Select
5. Select an Authentication Type from the drop-down menu:

   Basic	Authentication encrypted as a Base64-encoded string.
   Digest	Authentication encrypted using Message-Digest algorithm 5 (MD5) encoding
   NTLM	Simple challenge/response authentication used between Windows NT clients and servers
   Login	Use with script-based tests (e.g. Transaction) when the remote server requires application-level authentication, such as through a  javascript web form. Authentication requests must be made explicitly by the script, using the macros ${Username} and ${Password} to reference the plain-text credential values. Learn more about transaction commands and macros

6. To store your changes, click the Save button in the Product, Folder or Test.

Add a New Credential

1. Click + Add User Name and Password
2. Click + Create New
3. If you want to add the new credential to the Library so it can be easily added to other test configurations, complete the Credential Name field, and optionally add a Description and any Labels. Otherwise, deselect the Save to Library option.
4. Input the User Name and Password of this credential
5. Click Save
6. Select an Authentication Type from the drop-down menu:

   Basic	Authentication encrypted as a Base64-encoded string.
   Digest	Authentication encrypted using Message-Digest algorithm 5 (MD5) encoding
   NTLM	Simple challenge/response authentication used between Windows NT clients and servers
   Login	Use with script-based tests (e.g. Transaction) when the remote server requires application-level authentication, such as through a  javascript web form. Authentication requests must be made explicitly by the script, using the macros ${Username} and ${Password} to reference the plain-text credential values. Learn more about transaction commands and macros

7. To store your changes, click the Save button in the Product, Folder or Test.

Adding Tokens

You can add Tokens at the Product, Folder or Test level in order to test resources that support Token -based authentication, such as APIs. Note that Tokens must first be created in the Credentials Library.

1. Click + Add Tokens
2. A list of tokens in the Credentials Library is displayed. Check the box next to the desired token(s).
3. Click Select

After completing these steps, you must also add a Custom HTTP Request Header per the instructions in the following section. When completing the "Value" field, input the token macro as follows, replacing "token name" with the name of the token added previously:

${token(token name)}

Assign HTTP Request Headers

Catchpoint allows you to choose from a list of 15 common HTTP request headers, and you can specify up to five additional custom headers. Follow the steps below for each Request Header that you want to add.

1. Click "+ HTTP Headers"
2. In the "Apply To" drop-down menu, select "Test URL" or "Child Host". If you select "Child Host" you must input a hostname.
3. In the "Field" drop-down menu, select a header field name to configure (see description of each option below), or choose "Custom" if you with to define your own header field. If you select "Custom" you must input the name of your Custom field.
4. In the "Value" input box, input the data to assign to this Header field. You can use Macros in this field. See Test Macros for more information.
5. To store your changes, click the Save button on the Product, Folder or Test.