- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
11-17-2022 05:30 AM
It is of my understanding that you can set server configurations on the XSOAR Server and on a single engine to provide the links and responses through the engine that acts as a proxy. In a single server deployment with multiple engines can you manage this dynamically ? Essentially, can you have two engines with this configuration (Bind Address and Port etc) and send communication tasks based on which environment the end user is located with the allocated link of the engine ?
Another question on a similar direction is can you define what engine will be responsible for what specific task in playbook. An example of this is a task that uses a specific Integration in the "Advanced tab >> Using....." that you can dynamically choose what engine will be used rather than defining it on the Integrations Menu.
Many thanks
11-17-2022 04:58 PM
Hi @michaelsysec242, the link configuration can be set once only and that applies to all communication tasks created on the platform. Refer - https://docs.paloaltonetworks.com/cortex/cortex-xsoar/6-9/cortex-xsoar-admin/engines/configure-engin....
In short, that is not supported. Feel free to raise a feature request here - https://xsoar.ideas.aha.io/ideas.
11-17-2022 04:58 PM
Hi @michaelsysec242, the link configuration can be set once only and that applies to all communication tasks created on the platform. Refer - https://docs.paloaltonetworks.com/cortex/cortex-xsoar/6-9/cortex-xsoar-admin/engines/configure-engin....
In short, that is not supported. Feel free to raise a feature request here - https://xsoar.ideas.aha.io/ideas.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!