Introducing Proxy Support for HTTP Tasks in Orkes Conductor

Enterprise environments often enforce strict network controls and security measures. That's why we're excited to announce comprehensive Proxy Support for all HTTP tasks in Orkes Conductor. With Proxy Support, it is easier than ever to integrate Orkes Conductor into your enterprise infrastructure.

Why use Proxy Support?

In many enterprise environments, access to the Internet or even internal networks is restricted for security reasons. Instead, all outbound HTTP requests must go through a proxy server that acts as an intermediary, providing:

• Security filtering: Block malicious websites and content
• Access control: Enforce company policies on internet usage
• Monitoring and logging: Track all outbound requests for compliance
• Bandwidth management: Control and optimize network usage

Previously, configuring Orkes Conductor to work with corporate proxies required complex workarounds. Now, with our new built-in Proxy Support, you can seamlessly integrate Conductor into your existing network infrastructure.

Key features

All HTTP and HTTP Poll tasks in Orkes Conductor can be configured to run via a proxy server. This applies in all cases, no matter if they are real-time, synchronous API flows or asynchronous workflows that use Orkes’ built-in system HTTP task workers.

Here’s what you can expect from our Proxy Support:

• HTTP and HTTPS proxy protocols—Works with most enterprise proxy setups.
• Authentication support—Username/password authentication for secured proxies.
• Flexible bypass rules—Configuration rules for which hosts can bypass the proxy.
• Universal support—Proxy support for both built-in HTTP workers and direct synchronous HTTP calls.

How to get started?

Proxy Support for HTTP tasks eliminates a significant barrier to seamlessly integrating Conductor into your secure network infrastructure.

You can easily get started with using proxies by following these steps:

1. Get proxy details from your network or security team.
2. Add the required proxy properties to the Conductor server.
3. Test proxy routing using a simple HTTP workflow.

Plus, with simple configuration properties, you can configure proxy authentication, optimize the traffic, and more. Experience the flexibility and power of Conductor’s workflow orchestration without worrying about enterprise security.

Ready to get started? Check out the documentation for more information!