Configure Access to Communication Tasks through an Engine - Administrator Guide - 6.10 - Cortex XSOAR - Cortex - Security Operations

Cortex XSOAR Administrator Guide

Product
Cortex XSOAR
Version
6.10
Creation date
2022-10-13
Last date published
2024-04-08
End_of_Life
EoL
Category
Administrator Guide
Abstract

Enable users who can’t access the Cortex XSOAR server to fill out forms for communication tasks. Use engine as a proxy.

You can use engines to enable users who do not have access to the Cortex XSOAR server to access the forms sent out in communication tasks. In such instances, the engine serves as a proxy and passes the information in the forms to the Cortex XSOAR server. To use your own certificate instead of the default self-signed certificate, configure an engine to use custom certificates.

Prerequisites

Ensure that the BindAddress in the engine d1.conf file is configured to a port on which the engine can listen. The engine server address and the configured BindAddress are required to enable external users to communicate with the Cortex XSOAR server.

  1. Navigate to SettingsAboutTroubleshooting.

  2. Click Add Server Configuration.

    Key

    Value

    data.collection.external.link

    The address (including the https prefix) of the engine used for external user communication.

    condition.ask.external.link

    The address (including the https prefix) of the engine used for external user communication.

  3. Click Save.