When activating our new experimental Proxy Connector, there will be a new Connector Type Proxy v2. The configuration is similar to the existing Proxy Connectors, but uses a different technology in the background. Mutual SSL is not yet supported
Note: As soon as the new Proxy Connector has reached the ‘Released’ Lifecycle stage, it will replace the existing one, and all existing Connectors will automatically use the new one. You won’t need to change your applications
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 as a 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.
NOTE: To blacklist cookies ‘Cookie’ needs to be whitelisted for the Request headers.
To use this connector, you can request the following route ‘https://<your simplifier instance>/client/1.0/proxy/<connectorname>?SimplifierToken=xxxxxxxxxxxxxxx‘ (old Proxy Connector) or ‘https://<your simplifier instance>/client/2.0/proxy/<connectorname>?SimplifierToken=xxxxxxxxxxxxxxx’ (Proxy v2 Connector)
via HTTP Post.
The Simplifier Token will be generated after login of if the application being used as anonymous by starting your application.
