Service Options

Service options gives a way to configure how requests will be sent outside the service definition itself.

For example, web services are hosted on the server while you need to authenticate yourself before calling. You need to send special token via HTTP headers.

In request editor, you can activate the service option panel by clicking on the btn options button.

Service Options panel will be shown on the right side of the window:

service options

General Options

Authentication

Here you can choose the authentication method and credentials to use. By default, requests will be sent without authentication: Anonymous. You can choose a different authentication method according to the service configuration (you need to talk with dev or ops team). In the real world, most of the services are using Anonymous and Basic Authentications, over HTTP or HTTPS.

Hummingbird supports following authentication types:

Basic authentication: User name and password sent with the header. When using this type of authentication, you need to specify a credential of that type from Test Settings.
Digest authentication: Limited integrity protection for the messages. When using this type of authentication, you need to specify a credential of that type from Test Settings.
NTLM Authentication: Authenticate using NTML with your current Windows Identity, if failed automatically switch to Windows Authentication. For security reasons, it is not possible to use another credential (username/password).
Windows Authentication: Authenticate using Windows Integrated Authentication with your current Windows Identity. For security reasons, it is not possible to use another credential (username/password)

Pre-Emptive Authentication

Server may configured using pre-emptive authentication instead of using default authentication scheme. When Pre-emptive is activated, username and password will be sent directly without expecting http 100 continue.

If server is configured for Basic Authentication with Pre-Emptive, activate this option when sending requests.

SOAP Options

These options are only used by Soap Client for SOAP Web services

Soap Message Encoding

By default, soap messages are sent with XML. For large responses with usually attachments server may configured as MToM. If the server expected request/response to be sent using MToM (Content-Type: application/xop), please activate this option

Soap Message Version

Most of web services are Soap 1.1, and you may meet some web service using Soap 1.2 protocol. For these services, make sure that Soap 1.2 is activated.

Note
When services are imported using Extension Designer, Hummingbird recognizes automatically the soap 1.2 messages from WSDL and will select SOAP 1.2 by default.

Custom Http Headers

In some cases, the server side expect some special HTTP headers, for example: Cookies, Token, and Session Id. If these headers are required, you can add them here. they will be sent with the request.