Configure the network settings if your DTP infrastructure is deployed to an environment using forward and/or reverse proxies or if a cross-origin resource sharing (CORS) policy is enforced. Forward and reverse proxy servers are commonly used to cache static or frequently-requested files to improve performance. CORS defines which cross-origin request are allowed to improve network security.
To access the network settings, choose Settings from the gear icon menu and choose Network Settings from the Administration sidebar.
Cross-origin Resource Sharing Configuration
Specify a comma separated list of fully-qualified domain names in the Whitelist field to manually enable network access to DTP Enterprise Pack from different domains.
Cross-origin Resource Sharing (CORS) is a specification for allowing modern web browsers to circumvent the "same-origin policy" and share resources across domains. The same-origin policy is a security mechanism that protects users from malicious content by requiring browser requests to a website to go through the same domain serving the website. Because DTP Enterprise Pack is designed to be an integration point in the Parasoft ecosystem, CORS whitelist functionality has been exposed to allow for 3rd party integrations with DTP Enterprise Pack.
The CORS whitelist can be used to:
- Configure network aliases when DTP Enterprise Pack is running on a machine with multiple hostnames.
- Configure hostnames for 3rd party websites/intranet pages that integrate with DTP Enterprise Pack.
- Configure reverse proxy/load balancer hostnames when DTP Enterprise Pack is behind a complex network configuration (see Reverse Proxy). Reverse proxy settings should be used for end-to-end reverse proxy support, when the reverse proxy settings are used the hostname is automatically added to the whitelist and does not need to be configured manually.
The whitelist should be a comma separated list of hostnames (or origins) that are allowed to make cross-origin requests to DTP Enterprise Pack. You should provide a hostname, fully-qualified domain name, or IP address. Do not include the protocol or port.
Click Save when finished.
Enable the Enable forward proxy option and specify the hostname and port of the proxy server. If the proxy server requires authentication, a username and password can be configured to authenticate with the proxy server.
Enabling the proxy server sends HTTP(S) requests through the proxy.When enabled, HTTP(S) requests to the Marketplace server (configured in the Marketplace Settings) and any requests made by http request nodes (see Working with Nodes) will be sent through the proxy.
- You can specify a list of hostnames, fully-qualified domain names, and/or IP addresses in the No Proxy Hosts field to avoid using the proxy for all HTTP(S) requests to those hosts.
- Click Save when finished.
If your organization uses a reverse proxy server, you can enable the Enable reverse proxy option and configure access to DTP through the reverse proxy server. See Reverse Proxy Support for additional information about configuring Enterprise Pack to function in a reverse proxy environment.
Configure the following settings:
- Protocol: Choose the protocol your reverse proxy server communicates through.
- Hostname: Specify the hostname of the reverse proxy server.
- DTP Port: Specify the port number that the reverse proxy should use to access DTP.
- DTP Context Path: Specify a path that the reverse proxy should use to access DTP. The value in this field is the path prefix for the Extension Designer Context Path value. The value should start with a forward slash (
/). In the example above, you would access DTP at
grsis the path to Report Center, DTP's primary web application).
- Extension Designer Context Port: Specify the port number that the reverse proxy should use to connect to Extension Designer.
- Extension Designer Context Path: Specify a path that the reverse proxy should use to access Enterprise Pack. The value in this field should start with a forward slash (
/) and the value the value in the DTP Context Path field. In the example above, you would access Extension Designer at