Versions Compared

Old Version 2

changes.mady.by.user SS Doc Editor

Saved on

compared with

New Version Current

changes.mady.by.user SS Doc Editor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Server Authentication

Server authentication refers to any machine, operating system, or domain-level authentication. It includes Basic, Windows Integrated (e.g., NTLM), or other Kerberos authentication.

To configure server authentication, provide credentials the tested website recognizes and use the Authentication node in the Workflow Tree to enter the supplied credentials. You can also paste data (from Excel) into the authentication grid. The Domain field might be optional, depending on your server.


Note
Note 1: If you are in the Authentication section and need to configure the form or any other application authentication described below, click Go to Forms Authentication on the toolbar.
Note
Note 2: By default, every new VU will use a subsequent set of credentials. If the number of VUs exceeds the number of credentials, they are assigned using a round-robin algorithm. For example, if you have ten rows in the Authentication grid and emulate 20 VUs, then VU1 and VU11 will use row 1, VU2, and VU12 will use row 2, and so on. To change this behavior to On-Demand, change the VU-to-row property to On-Demand. For more about on-demand binding, see here.

Authentication is configured per Test. Credentials created in one test case are used in all test cases.

Tip
titleOAuth2 on mobile appstoken refresh

For applications using OAuth2 authentication, the credentials in the Server Authentication table will be used to automatically refresh the Bearer token automatically. This is helpful for mobile app testing.

Host-specific credentials

Some web applications use several hosts that require different credentials for authentication. In order to support such authentication schema, you need to enable host-specific credentials. To do so, set the Show host column? property to Yes (a). The Host column (b) appears in the authentication grid. For every set of credentials, enter a host to which the credentials will be submitted.


Client Certificates

In some cases, every VU needs a unique client certificate to communicate with a server. Client certificate files should be accessible from the StresStimulus machine. For example, in the test folder, create a subfolder, Certificates, and save the certificate files. Set the Show certificate column? to Yes (c). The Certificate column (d) appears in the authentication grid.

For each VU row, enter the name of the certificate files in the Certificates folder. Alternatively, enter a full path of the certificate file if it is located in a different folder.


Info
titleNote:

If the Host column is not empty, then the client certificate will only be applied to requests to the given host.

Note
titleNote:

The UserName and Password column can be left blank when using the Certificates feature.

Warning
titleNote:

When using the Certificates feature, the Use a shared connection pool for all VUs?  must be set to No to prevent VUs from using connections authenticated by other VUs. For more, see connection pools.



Application Authentication

Application-level authentication refers to the authentication method inside the web application (e.g., Form authentication). The test case will store the credentials entered during recording. By default, these credentials will be used for all VUs. To test VUs with different credentials, you need to:

  • Provide a set of credentials that the tested website recognizes.
  • Create a dataset, populate it with the provided credentials, and parameterize the appropriate request as described below:


1. click Create Authentication Dataset on the toolbar in the Datasets section . The Credentials dataset will be created. If your authentication process includes additional properties, such as security questions, you can edit the Credentials dataset structure by adding additional fields (see Datasets ).  

2. Populate the authentication dataset by entering them manually, pasting the data (from Excel), or importing from a data source.

3. Find the login request in the test case (it is usually one of the first POST requests). To do so:

a. Click Find Session by Content or hit <Crl+F>

b. Enter one of the credentials you used in recording (e.g., a username, email address, or password).

c. The first highlighted session is a login request. Select it.


...