HTTP Adapter Configuration - Basic

Edit online

Use this tab to specify basic communications information for HTTP connections. You can set up a configured Proxy Adapter to multiple Secure Proxy engines so you can push one adapter configuration from the Configuration Manager to multiple engine instances.

Before you can click the Advanced or Properties tabs, you must specify Adapter Name and Listen Port. Refer to the field definitions in the following table.

To manage Secure Proxy engines with a configured Adapter:
  • Click Add New Engine + to add a new engine to the configured adapter.
  • Click Copy icon to copy an existing engine to the configured adapter.
  • Click Remove icon to remove a specific engine to the configured adapter.

Field Name

Description

Adapter Name

Name to assign to the adapter you create. Valid values are 1-150 alphanumeric characters with no spaces. Special characters allowed are period (.), dash (-), and underscore (_).

Description

Description up to 255 characters to help identify the adapter you create.

Listen Port

Port number to use to listen for inbound connections. Default=13640. Valid values include 1-65535.

Netmap

Name of the netmap to associate with the adapter you are defining. If the netmap has not been created, click + to add the netmap.

Routing Type

Select the Routing Type to identify how a routing node for each of the HTTP inbound nodes from the list of outbound nodes in the netmap.

Select one of the following choices:
  • Standard
  • Userid based — Only routes to a matching outbound node and matching routingNodeName identified in the LDAP. If the outbound node can not be determined, it will fail.
  • Userid based with a default fallback — Routes to a matching outbound node and matching routingNodeName identified in the LDAP; however, if there is no associated outbound node found, the will make the connection to the default outbound node.
  • Inbound node based routing — Only routes to a matching inbound node for Inbound node-based routing. If the inbound node can not be determined, it will fail.
  • Inbound node based routing with default — Routes to a matching inbound node for Inbound node-based routing; however, if there is no associated routing node found, the HTTP proxy will make the connection to the default outbound node.

Standard Routing Node

Standard Routing Node identifies the name of the HTTP secure server where the inbound node connections are routed, after connecting to Secure Proxy. Select this value from a pull-down list.

Support HTML Rewrite

Enable Support HTML Rewrite to rewrite URLs within the HTML returned by the outbound node. HTML Rewrite must also be defined and enabled on the netmap.

Engine

Engine identifies the Secure Proxy server in the DMZ where the adapter listens for inbound connections and routes the connection to an outbound node. Select an engine from the list. You must define an engine before you can create an adapter.

Inbound PS

Inbound Perimeter Server. Select the perimeter server for the inbound connection in the Perimeter Server Mapping - Inbound Perimeter Server field. To use a remote perimeter server, you must define the server before you associate it with an inbound connection.

Outbound PS

Outbound Perimeter Server. Select the perimeter server to use for the outbound connection in the Perimeter Server Mapping - Outbound Perimeter Server field. To use a remote perimeter server, you must define it before you can associate it with an outbound connection.

EA PS

External Authentication Perimeter Server. Select the perimeter server to use for the Sterling External Authentication Server connection in the Perimeter Server Mapping - External Authentication Perimeter Server field. To use a remote perimeter server, you must define it before you can associate it with an Secure Proxy connection.

EA Server

External Authentication Server. External Authentication Server identifies the server to use. Select the server from the pull-down list. You must define a Sterling External Authentication Server before you can select the server from the list.
ICAP Server Select one of the already defined ICAP servers, which will be used to process anti virus and malware scanning requests.
ICAP PS

Select the ICAP Perimeter Server (PS), which will be used to connect to ICAP Server per engine basis for a given HTTP Adapter.

Startup Mode
Startup Mode identifies how the adapter is started. Values are:
  • auto - starts the adapter as soon as it is pushed to the engine
  • manual - requires that the adapter be manually started