Configuration

Configuration Overview

The purpose of the Configuration action is to allow reconfiguration of parts of the test data that can be changed after a test is running as an action.

Types of Configuration Actions:

  • MTLS
  • Proxy
  • HTTP AUTH

MTLS

MTLS Overview

MTLS is a mutual authentication mechanism. By validating that both parties have the correct private key, MTLS ensures that the entities at both ends of a network connection are who they claim to be. Additional verification is provided by the information included inside their respective TLS certificates.

How Does MTLS Assist with Functionize?

Functionize improves the security of your backend apps by supporting mutual TLS (mTLS) via our robust proxy service. This feature guarantees that the client and server both authenticate each other's certificates, resulting in a bidirectional verification process. Our proxy operates as a fortified gateway by enforcing mTLS, enabling only validated clients with the right certificates to interact with your backend services.

When using our testing software, users must undertake a simple method to enable transparent mutual TLS (mTLS) authentication. Here, you will be prompted to enter your certificate chain and private key. By providing these credentials, you configure the testing environment to use mTLS, ensuring that both the client and server participating in your backend services authenticate each other securely.


Adding an MTLS Configuration Action to a Test Case

Functionize provides multiple ways to add actions to test cases. You can insert actions directly from the Test Detail page or Slider View.

Inserting an MTLS Configuration Action via the Test Detail Page:

  1. Open a test from the functional test list in any project.
  2. Hover over any action; an Insert Action ⊕ icon will appear, giving the option to insert a new action at the selected location.
  3. Click the Insert Action ⊕ icon to view the Insert menu and select Configuration to add a Configuration action.
  4. In the Insert Config window, select MTLS from the dropdown list.


  5. Enter the value in the MTLS client Key field and insert the private key.
    • Note for MTLS client Key: Clients can provide their public key and certificate to the server, which validates that the request originates from a recognized client and that the private key corresponds to the public key that the client shared. The client key is included in a PEM encoded file, which begins with “-----BEGIN PRIVATE KEY -----” and ends with “-----END PRIVATE KEY-----“.
  6. Enter the value in the MTLS client certificate (PEM format) field and click on the Insert button.
    • Note for MTLS client certificate (PEM format): Start with the server certificate, then the intermediate certificates in the sequence necessary to construct a trust chain up to the root certificate. The root certificate should come last in the chain. This ordered chain enables the mTLS system to validate the server certificate’s trustworthiness against the intermediate and root certificates, delivering a safe and authenticated communication route for your testing operations.
  7. The MTLS Configuration Action is now added to the test, and the action will be shown in a grayed-out color and include a NEW tag under the test step number.

    Note: This can also be added via Slider View.


Proxy

Proxy Overview

A proxy server acts as a gateway between end users and the internet. It's an intermediary server that separates end users from the websites they browse. Proxy servers provide varying levels of functionality, security, and privacy depending on the use case, needs, or company policy.

When using a proxy server, internet traffic flows through the proxy server on its way to the requested address. The request then comes back through the same proxy server, with exceptions to this rule, and finally, the proxy server forwards the data received from the website to the end user.

How Does Proxy Assist with Functionize?

Customer applications behind a firewall require the use of a proxy to access the AUT (Application Under Test). Since not all applications may require a proxy or may require multiple proxies, a user must set up the proxy on a per-project basis.

Note: We can help users set up their proxy settings so that the application(s) under development are accessible from our execution servers.

Adding a Proxy Configuration Action to a Test Case

Functionize provides multiple ways to add actions to test cases. You can insert actions directly from the Test Detail page or Slider View.

Inserting a Proxy Configuration Action via Slider View:

  1. Open the Slider View for a test in any project.
  2. Hover over any action; an Insert Action ⊕ icon will appear, giving the option to insert a new action at the selected location.
  3. Click the Insert Action ⊕ icon to view the Insert menu and select Configuration to add a Configuration action.
  4. In the Insert Config window, select Proxy from the dropdown list.
  5. Enter the details in the Proxy field and click on the Insert button.
  6. The Proxy Configuration Action is now added to the test.

HTTP AUTH

HTTP AUTH Overview

HTTP Authentication (HTTP AUTH) is a method used by web servers to verify the identity of clients attempting to access protected resources on a website or web application. It’s a standard protocol defined in the HTTP specification that enables servers to request credentials from clients and authenticate them before granting access.

HTTP AUTH is crucial for securing sensitive areas of websites and web applications, ensuring that only authorized users can access protected resources. It’s widely supported by web servers and clients, making it a fundamental mechanism for controlling access to online services.

How Does HTTP AUTH Assist with Functionize?

Functionize is a platform that provides solutions for web applications. HTTP AUTH can assist Functionize where web applications require user authentication to access certain functionalities or protected resources.

Adding an HTTP AUTH Configuration Action to a Test Case

Functionize provides multiple ways to add actions to test cases. You can insert actions directly from the Test Detail page or Slider View.

Inserting an HTTP AUTH Configuration Action via Slider View:

  1. Open the Slider View for a test in any project.
  2. Hover over any action; an Insert Action ⊕ icon will appear, giving the option to insert a new action at the selected location.
  3. Click the Insert Action ⊕ icon to view the Insert menu and select Configuration to add a Configuration action.
  4. In the Insert Config window, select HTTP AUTH from the dropdown list.
  5. Enter the details in the Default HTTP Authentication field.
  6. Click the Insert button.
  7. The HTTP AUTH Configuration Action is now added to the test.


Adding Multiple MTLS Certs Via TDM Data Source in a Test

Creating a Data Source:

  1. Select the TDM tab in the navigation menu. Once the page loads, a list of previous data sources will appear.
  2. To add a data source directly from this page, select the Add New Data Source button.
    TDMb2.png
  3. In the Add New Data Source pop-up window, enter the Data Source Name, select the Type (CSV, DB, Excel, JSON, or Google Sheet), click the File button to select the file to upload, select the Members from the list who can access this data source, and then click Submit.


    Note: For reference, a screenshot of the data present in the JSON-TDM.csv file can be attached. 

  4. A new data source is created with the column name test_configuration.



Mapping the TDM Data Source in the Test at the Configuration Action:

  1. Select the action and expand to see Action Details.
  2. Click Add Test Data.
  3. Select the Data Source or add a data source as needed.
  4. Select the Column that you'd like to map to the action.
  5. Select Read or Write Mapping Type.
  6. Click Next, select the Attribute as Add Custom, and input the column name of the data source (test_configuration), then click the OK button.
  7. The TDM data source is attached to the configuration action.