Configure HTTP (HTTPS)

You can use HTTP service port types to simulate virtual HTTP services.

Use the HTTP service port type options Client and Server to define your service ports. A client sends a request; a server sends a response. For information on how to set up service ports, see chapter "Create and edit service ports".

Server

The service port listens for incoming requests on the defined port. You can specify the following attributes for the server:

Attribute

Description

IP

Specify an IP address that the service port listens to.

If you don't enter an IP address, the service port uses the default network interface (local host).

Port

Enter the server port.

Soap

Select the checkbox to use SOAP protocol with HTTP.

Use Secure Connection

Select the checkbox to use Secure Sockets Layer (SSL).

Client pfx File Path

Enter the Windows file path to the PFX file that identifies the user.

A PFX file contains your certificates and corresponding private keys.

Client pfx File Password

Enter the password for the Client pfx File Path.

HTTP Server

Client

The service port sends messages to the configured endpoint.

You can specify the following attributes for the client:

Attribute

Description

Url

Enter the URL to the HTTP service.

Security Protocol

Select a security protocol for authentication.

The following protocols are available: Default (most recently used protocol), Ssl3, Tls, Tls11, Tls12.

Soap

Select the checkbox to use the SOAP protocol with HTTP.

Client pfx File Path

Specify the Windows file path to the PFX file that identifies the user.

A PFX file contains your certificates and corresponding private keys.

Client pfx File Password

Enter the password for the Client pfx File Path.

Proxy: Use System Default

Select this checkbox to use the proxy definitions (LAN settings) you defined in Microsoft Internet Explorer.

Proxy: Uri

If you don't enable Proxy: Use System Default, enter a URL here.

For example: http://52.174.157.85:1111

Proxy: Use Default Credentials

Select this check box to use the logged-in Windows user.

Proxy: User

Define the user. This setting only applies if you haven't enabled Proxy: Use System Default.

Proxy: Password

Define the user password. This setting only applies if you haven't enabled Proxy: Use System Default.

Proxy: Domain

Define the domain. This setting only applies if you haven't enabled Proxy: Use System Default.

If you select the check box Soap for an HTTP service port, the system sets the content type header for inbound and outbound messages to XML and verifies whether the SOAPAction header exists.

HTTP Client

Use REST

OSV supports RESTful services, i.e. services that implement the REST architecture. OSV detects the message format automatically. You don't need to do any additional configurations. For more information on supported message formats, see chapter "Set message formats". .

Use HTTPS

If you want to test locally on your own system via proxies, you must use the fully qualified name (FQN) of your computer.

When forwarding messages, the OSV environment acts as a client and must authenticate itself to a webservice or another endpoint.

Select Use Secure Connection, to start the HTTP service port in HTTPS mode.

Additionally, you have to adjust the following settings for HTTPS mode:

  1. Bind the fingerprint of the PFX file certificate (=certhash) to the port you defined for the service port. Use netsh in the command line. For instance:

    • Add binding:

      netsh http add sslcert ipport=0.0.0.0:1234 certhash=7eb35dff000ea90b72d46952e3016c8fad3213e1 appid={86476d42-f4f3-48f5-9367-ff60f2ed2cdd} clientcertnegotiation=disable

    • Delete binding:

      netsh http delete sslcert ipport=0.0.0.0:1234

    • Show binding:

      netsh http show sslcert ipport=0.0.0.0:1234

  2. Install the PFX file in the Windows certificate store (LocalMachine/My).

  3. Make sure that the PFX file is trusted in one of the following ways:

    • Ensure that there is a certificate in LocalMachine/TrustedRootStore that is identical to the one you installed.

    • Ensure that there is a certificate in LocalMachine/TrustedRootStore for which there is a certificate chain. That means the PFX file was signed by someone who is already in LocalMachine/TrustedRootStore.