Basic auth and custom HTTP headers

Adding and Using Basic Auth

If your test environment is protected by HTTP basic auth, you can now configure mabl tests with basic auth credentials. To configure basic auth:

  1. Enter your basic auth credentials by clicking configure on the left nav, then click the Credentials tab.

  2. From the Credentials tab, click the credentials button.

  1. On the new page that appears, titled "Add new credentials," add your credential name, username and password. Then click the "Save" button.
  1. After saving your basic auth credentials, edit a plan and enable the HTTP basic auth required toggle under the Advanced section of the plan.

  2. Scroll to the bottom of the page to find the basic auth settings.

  1. Turn basic auth on, and select your credentials from the dropdown that appears.
  1. Before leaving the page, be sure to click the "Save" button at the bottom.

Note: Using Basic Auth and Application Logins

It is possible to use both HTTP basic auth and application logins at the same time. If basic auth credentials are specified, these will be sent at the HTTP layer with all requests to your test site. If application credentials are also specified, mabl will attempt to login to your application by locating a login form and entering the given credentials.

Adding Custom HTTP Headers

You can now configure mabl to pass custom HTTP headers with each request. These custom headers may be used for authentication or to exercise some specific behavior of your application. To specify custom HTTP headers:

  1. Edit a plan by navigating to the test panel and selecting a plan. Then, select "Edit."
  1. Scroll down within the edit window, then enable the Send custom HTTP headers toggle under the Advanced section. Finally, add one or more header key-value pairs.
  1. Before leaving the page, be sure to click the "Save" button at the bottom.

Updated 3 months ago

Basic auth and custom HTTP headers

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.