Common headers or authentication settings can be configured in an environment and applied to all requests within a test. When specified, default headers and auth settings will be automatically included in each request step for your test. Variables can be used, but will only be evaluated at the beginning of the test run, before the first step is executed.
Basic authentication, oAuth 1.0a, and client certificates can be configured to be applied to all requests within a test. This setting is inherited from a parent environment if specified, but can be overridden on a per-environment or per-request basis.
Default headers are useful for specifying header values like user agents, content types, and OAuth 2 bearer tokens that apply to all requests within a test. If a header is specified in an environment but also a request, the request-specific value will take precedence when the test is executed. This setting is also inherited from a parent environment if specified, but can be overridden on a per-test basis.
Custom client certificates can be stored to be used by requests within a test. Create a PEM-formatted, non password protected certificate and paste it into the text area. Once saved you'll be able to add it to requests in your test by selecting Add Client Certificate under the Authentication options of an individual request or environment.
Client Certificate support requires a qualifying plan. Contact sales to get started.