This topic explains how to configure message proxies that send and receive messages over HTTP (including HTTPS). 

In this section: 

You will need the host, port, and path of the service you are targeting in order to set up basic HTTP connection options. Use the settings you would normally use to directly message the service. 

Connection Settings

To specify basic HTTP Reverse proxy connection options, set the following service and listening details in the Proxy Settings Connection tab.

Proxy Settings (incoming) 

These settings specify where messages from the client should connect in order to communicate with the application under test. 

Primary Connection (outgoing) & Secondary Connection (outgoing)

Options

Mode: Allows you to set the active forwarding connection when a primary and secondary connection exist. For example, during a recording session, a message proxy may forward to the live service as the primary connection and fall back to a virtual service as a secondary connection. In this case, you can set the HTTP mode to Primary and enable Use other connection if selected mode fails.

Once recording is complete and new virtual assets are generated, you may want to re-configure the proxy to forward to the virtual service first and fall back to the live service if a failure occurs. This change can be quickly applied by right-clicking the proxy and switching the HTTP mode to "secondary". The failover will be adjusted accordingly at runtime.

Use other connection if selected mode fails: Enable this option if you want traffic to be redirected to the backup proxy endpoint when the active connection (as determined by the Mode selected above) fails. The connection will be considered "failed" if the response status code is 400 level or higher.

If this option is not enabled, the active connection will be used for recording.

If this option is enabled, select a recording option from the Record dropdown:

• Both connections: Records traffic for both the primary and secondary connections. Error messages from the active connection will not be recorded; instead the messages will be sent to the backup connection and the responses will be recorded. Errors reported by the backup will be recorded.
• Primary connection only: Records traffic for the active connection. Does not record errors.
• Secondary connection only: Records traffic for the backup connection, including errors.

Security Tab Settings

The Service SSL section needs to be completed only if the service you are working with uses SSL.

If the service being virtualized  uses SSL and/or other authentication (basic/digest, Kerberos, NTLM), additional configuration may be required.

For details on completing the Service SSL fields immediately below these fields, see Security Configuration.

Proxy Server Tab Settings

You can specify a server for the message proxy in this tab, which enables you to configure a different proxy server for traffic to and from different message proxies. This configuration provides control over which proxy server handles traffic between the application under test and a specific message proxy. 

To specify proxy settings at this level, provide the appropriate details in the proxy’s Proxy Server tab. 

SSL is not supported. 

Service Forward Path and Proxy Listen Path

In the simplest case, you can set Proxy listen path to the path of your service and leave Service forward path empty. With this configuration, the proxy will automatically forward all messages it receives on that path to the same path at the Service host and Service port. 

If you need the proxy to listen on a different path than the path of your service, set Service forward path to the actual path where you want received messages to be sent. The proxy will forward the path and any query parts to the target service. 

If the Proxy listen path and the Service forward path are different, then any segments in the request after the Proxy listen path will be appended to the forwarded request. The Proxy listen path is essentially being replaced with the Service forward path so that the entire path (as received by the proxy) gets sent to the service.

Using Wildcard Characters in Paths

You can use wildcard characters to specify dynamic path segments. For example, configuring the path as /path/*/service would enable the following paths to go to the same proxy: 

/path/1/service 

/path/2/service 

Wildcards can be used to replace an entire path segment. For example:

• /path/*/service — valid
• /path/1*2/service — not valid

The wildcard can only be used for one segment of the path. A path configured as /path/*/service will NOT match /path/1/2/service. If you want your path to match both /path/1/2/service and /path/3/4/service, use the pattern /path/*/*/service.

You can use the dynamic segment from the listen path as part of the forward path. There are two ways to do this:

• If you want traffic to be forwarded to the path where the request was received, leave the forward path empty.

• If the forward path is different and the dynamic value needs to be used, configure it using environment variable syntax. For example:
  listen path: /path/*/service
forward path: /asset/path/${1}/service

The dynamic listen path segments represented by the wildcards can be accessed using environment variable syntax. The occurrence of the wildcard is used as the variable name; in other words, the first occurrence of the wildcard is ${1}, the second is ${2}, the third is ${3}, etc.  In the following example, ${2} refers to the second occurrence of the wildcard (which was "bank" in the request path):

listen path: /path/*/service/*/account
forward path: /asset/path/${2}/service/${1}/account

request path: /path/1/service/bank/account
forward path: /asset/path/bank/service/1/account

Header Alterations

In most cases, the proxy will pass all headers directly to and from the target service. Some content-length related headers may be changed to suit how the proxy server works. For example, the proxy server doesn't support responding with the "chunked" transfer encoding and will replace "host" headers sent to match its own host name (however, it does support receiving chunked requests and chunked responses from the target service).

Setting the Target Service

A proxy can use a virtual or test asset on a server as its target service. 

1. Set the service host and port to that of the Virtualize Server where the virtual asset is deployed. If you want the proxy to forward to a virtual asset on the local server without consuming an HTTP connection, enter, host.virt.internal, localhost, or 127.0.0.1 rather than the actual hostname. When using localhost or 127.0.0.1, the service port must match the port Virtualize is deployed on; when using host.virt.internal, the service port is not used.
2. Set the proxy connection’s Service forward path to the virtual asset’s path (found in the virtual asset’s Transports> HTTP tab, under HTTP endpoint).
   

Chunking/Unchunking Behavior

The proxy supports receiving chunked requests and chunked responses from the target service. If a service response uses HTTP chunking, proxies will unchunk responses before they are returned to the original caller/AUT.

Additional HTTP Message Proxy Configuration

You can create a properties file to configure additional Reverse Proxy HTTP Listener settings. The properties file allows you to fine-tune Reverse Proxy HTTP Listener performance and specify additional SSL settings.

1. Create a plain text file and specify the properties you want to set (see Reverse Proxy HTTP Listener Message Proxy Performance Properties and Reverse Proxy HTTP Listener Message Proxy SSL Properties). 

2. Save the file to the VirtualAssets directory in your workspace and name it embeddedServer.properties.

The file will be read every time a proxy with a Reverse Proxy HTTP Listener is enabled.

Reverse Proxy HTTP Listener Properties

Reverse Proxy HTTP Listener Message Proxy Performance Properties

All properties are optional and non-integer values will be ignored.

Reverse Proxy HTTP Listener Message Proxy SSL Properties

Example: Sending Traffic to a Service

Assume that we want to create a message for a service that is normally accessed at http://example.parasoft.com:9080/BookStore. We could create an HTTP Reverse proxy with the settings: 

• Proxy listen path: /BookStore
• Service host:example.parasoft.com
• Service port: 9080
• Service forward path: [empty]
  

This configuration will listen on /BookStore and forward all traffic to the actual book store service.

If we wanted to listen on a path other than the service path, we would change the configuration of the proxy as follows:

• Service forward path: /BookStore
• Proxy listen path: /SomeOtherPath
  

This would route traffic from /SomeOtherPath on the proxy to the actual book store service. 

In both cases, all traffic that goes to those paths (including sub paths) is sent to the service. In the second example, traffic sent to /SomeOtherPath/SubPath would be sent to /BookStore/SubPath. Because queries are preserved, /SomeOtherPath?param=value would be sent to /BookStore?param=value.

Forwarding Requests to Services that Require Case-sensitive Header Names

If you are using the desktop's server, your message proxy headers will be lowercased and may fail to function properly when requests are forwarded to a service that requires case-sensitive HTTP header names.

You can create a _global.headers file in the /VirtualAssets/ directory and add the headers using the specific capitalization you want to pass. Right-click the server in the UI and re-deploy all virtual assets to begin using this file in your environment.

You can also address HTTP header capitalization issues for specific message proxies. Create a <proxy-name>.headers file in the /VirtualAssets/ directory and add the headers using the specific capitalization you want to pass for the specific proxy. This file will apply to specific proxy and override the global file. Right-click the server in the UI and re-deploy all virtual assets to begin using this file in your environment.

Example Headers File

X-AUTHORIZATION
ANOTHER-HEADER
HEADER3

Example: Sending Traffic to a Virtual Asset

A proxy can also send traffic to a virtual asset. In that case, enter the host and port information for the Virtualize Server as if were just another service.

For example, to send traffic to a virtual asset on a remote server, you might use: 

• Proxy listen path: /path
• Service host: virtualize.parasoft.com
• Service port: 9080
  

To send traffic to a virtual asset on a local server, you might use:

• Service host: [Virtualize]
• Service forward path: /path
  

The HTTP Reverse proxy makes no distinction between a virtual asset and an actual service. Both are configured the same way. However if the HTTP Reverse proxy is sending to localhost, you must specify Service forward path because the proxy doesn't allow forwarding to itself.

Security Configuration

There are two aspects of configuration for security: 

• If the service to which you are forwarding the traffic uses SSL and/or access authentication, you need to perform proxy-level configuration (from the proxy’s UI controls).
• If the AUT uses SSL and/or access authentication, you need to perform server-level Configuration (for the Tomcat-based server).

Depending on your configuration, you configure either security setting or both.

Proxy-level Configuration

Proxy-level security configuration—which is relevant if the service to which you are forwarding the traffic uses SSL and/or access authentication—covers:

• SSL
• Basic/Digest Authentication
• NTLM Authentication
• Kerberos Authentication

SSL

For SSL, additional settings are required. In the lower part of the configuration panel, you need to specify whether to:

• Enable trust for self signed certificates.
• Enable trust for all certificate.
• Set a trust store to validate server certificates.

Additionally, you need to provide the information needed to use a specific key store and certificate so Parasoft can determine which certificate to present to a server (e.g., for 2-way SSL).

SSL Configuration Panel Fields

Note that the Truststore configuration (described below) is applicable only if Trust all server certificates and Accept self-signed certificates are both unselected.

Keystore Configuration Panel Fields

After completing the keystore detail, click the Load and choose the certificate alias to present to the server from the Certificate drop-down. If the Certificate dropdown is not populated when you click Load, you may have entered the incorrect password or keystore type.

Truststore Configuration Panel Fields

These fields are applicable only if Trust all and Accept self-signed certificates (described above) are both unselected.

NTLM Settings Panel Fields

Kerberos Panel Fields

Basic/Digest Authentication

If the application under test provides Basic and Digest authentication credentials as part of the request and transmits them as part of the HTTP header, the proxy will pass them along to the service unmodified (the same way it handles other HTTP headers). 

NTLM Authentication

If your service requires NTLM authentication, provide the username/password in the NTLM section.

Kerberos Authentication

If your service requires Kerberos authentication, set the Kerberos Service Principal in the Kerberos Authentication section.

Server-level Configuration

Server-level security configuration—which is relevant if the AUT uses SSL and/or access authentication—can involve:

• Configuring the Virtualize Server
• Using NTLM with WAFFLE
• Using Unsupported Configurations (Kerberos with WAFFLE, JAAS)

Configuring the SOAtest and Virtualize Server

You can change the default port number (9080), enable SSL, and configure other server settings. See Server Configuration for details. 

Using NTLM with WAFFLE

To use the third-party library WAFFLE for NTLM:

1. Copy the following jar files into tomcat's lib directory: jna.jar, platform.jar, wafflejna.jar.

2. Add the following to tomcat/conf/server.xml.
   
   

   <Context>
     <Valve className="waffle.apache.NegotiateAuthenticator" principalFormat="fqn" roleFormat="both"/> 
     <Realm className="waffle.apache.WindowsRealm" /> </Context> 

   Where is server.xml?

   If you installed SOAtest but not Virtualize: Launch SOAtest, ensure that at least one responder has been created, then modify the server.xml file at <INSTALL>/plugins/com.parasoft.ptest.libs.web_<VERSION>/root/tomcat/conf/server.xml

   If you installed Virtualize but not SOAtest: Launch Virtualize, ensure that at least one responder has been created, then modify the server.xml file at <INSTALL>/plugins/com.parasoft.ptest.libs.web_<VERSION>/root/tomcat/conf/server.xml

   If you installed Virtualize and SOAtest together: Launch Virtualize, ensure that at least one responder has been created, then modify the server.xml file at <INSTALL>/plugins/com.parasoft.ptest.libs.web_<VERSION>/root/tomcat/conf/server.xml

3. Add the following to tomcat/conf/web.xml.

   <security-role> 
     <role-name>Everyone</role-name> 
   </security-role> 
   <security-constraint> 
     <display-name>Waffle Security Constraint</display-name> 
     <web-resource-collection> 
       <web-resource-name>Protected Area</web-resource-name> 
       <url-pattern>/*</url-pattern> 
     </web-resource-collection> 
     <auth-constraint> 
       <role-name>Everyone</role-name> 
     </auth-constraint> 
   </security-constraint> 

4. Restart the server.

For more details, see the Single Sign-On: Tomcat Negotiate Authenticator (Kerberos + NTLM) w/ Waffle Tutorial and the WAFFLE home page.

Using Unsupported Configurations (Kerberos with WAFFLE, JAAS)

WAFFLE includes support for Kerberos authentication; see the WAFFLE home page for directions and support. 

JAAS is another option for configuring the Tomcat-based Virtualize Server to perform Kerberos authentication. Consult Tomcat for directions on how to use JAAS.