Proxy Connector

The Proxy Connector allows the usage of any HTTP services that are not based on specific protocol architectures, such as REST, SOAP, or OData.

Create a new connector and select ‘Proxy V2’ as the Connector type.

Within the specific data on the Endpoints tab, define the endpoint. Optionally, you can also define request headers and response headers to pass through and Request cookies to be removed. Also, relevant SSL settings can be made.

Connection Settings

Parameter	Description
Endpoint URL	The URL to the Service. This must be maintained
Header and Cookie Filters	Optionally, you can define filter lists for cookies, request or response headers. With “Blacklist”, the selected headers / cookies are removed, with “Whitelist” all except the selected are removed. The cookie filter only has an effect, if the Cookie header is not filtered out.
Enforce Headers	Optionally, you can also add hardcoded header values, which are always added to the request. If the original request contained a matching header, it is replaced with the enforced header.
Certificate Trust Options	Optionally, you decided which certificates should be trusted for SSL-Connections (Trusted Server Certificates).

With this option, the trust manager will not do any certificate validation, e.g., the validation of whether the issuer is also known or not. This could induce a security risk.

The new Proxy connector won’t support ignoring invalid SSL certificates if the certificate’s hostname does not match the actual hostname.

Security Settings

Parameter	Description
Login Method	Specifiy the Authentication needed for the Endpoint URL.
Certificate	Specify a certificate, if needed.

To use this connector, you need to request the route ‘https://<your simplifier instance>/client/2.0/proxy/<connectorname>?SimplifierToken=xxxxxxxxxxxxxxx’ (Proxy v2 Connector) in your Scripts / Client-side Business Objects via HTTP Post.

See our Standard Content’s Client-side Business Object ‘SF_SimplifierToken’ to retrieve the current Simplifier Token.