Update Long Running README and Description files (#31650)

* Update README.md

Clarify that some instructions are only for Cortex XSOAR 6.x.

* Update README.md

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* Update Long Running README and Description files

* RN

---------

Co-authored-by: davrahami <davrahami@paloaltonetworks.com>

Packs/EDL/Integrations/EDL/EDL_description.md

@@ -54,9 +54,14 @@ In a web browser, go to **http://<cortex-xsoar-server-address>:<listen_port>**.
 
 **Note**: The `Listen Port` parameter is required.
 
-1. In Cortex XSOAR, go to **Settings > About > Troubleshooting**.
-2. In the **Server Configuration** section, verify that the `instance.execute.external.<instance_name>` key is set to `true`. If this key does not exist, click **+ Add Server Configuration** and add the `instance.execute.external.<instance_name>` and set the value to `true`. See [this documentation](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
-3. In a web browser, go to: `https://*<xsoar_address>*/instance/execute/*<instance_name>*`
+1. For Cortex XSOAR  6.x only:
+   1. Navigate to **Settings > About > Troubleshooting**.
+   2. (For Cortex XSOAR 6.x only) In the **Server Configuration** section, verify that the `instance.execute.external.<instance_name>` key is set to `true`. If this key does not exist, click **+ Add Server Configuration** and add the `instance.execute.external.<instance_name>` and set the value to `true`. See [this documentation](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
+2.  In a web browser, go to:
+
+   - (For Cortex XSOAR 6.x) `https://*<xsoar_address>*/instance/execute/*<instance_name>*`
+   - (For Cortex XSOAR 8 or Cortex XSIAM) `https://ext-<tenant>.crtx.<region>.paloaltonetworks.com/xsoar/instance/execute/<instance-name>`
+
 
 In Multi Tenant environments, go to `https://<cortex-xsoar-address>/acc-<account name>/instance/execute/<instance_name>/`
 
@@ -95,4 +100,4 @@ Make sure you run the ***!export-indicators-list-update*** command for the first
 
 ### Important Notes:
 - If constantly using different queries for the same EDL instance through the *q* inline argument, it is recommended to use different instances of the EDL (one for each query), and set each one with a default query for better performance.
-- When using the *q* inline argument, the number of exported indicators is limited to 100,000 due to performance reasons. To export more than 100,000 indicators, create a new instance of the integration with the desired Indicator Query and List Size.
+- When using the *q* inline argument, the number of exported indicators is limited to 100,000 due to performance reasons. To export more than 100,000 indicators, create a new instance of the integration with the desired Indicator Query and List Size.

Packs/EDL/Integrations/EDL/README.md

@@ -157,11 +157,13 @@ In order to get the list of all available fields to search by, you can configure
 
 To access the Export Indicators service by instance name, make sure ***Instance execute external*** is enabled.
 
-1. In Cortex XSOAR, go to **Settings > About > Troubleshooting**.
-2. (Cortex XSOAR 6.x only) In the **Server Configuration** section, verify that the ***instance.execute.external*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add the *instance.execute.external* and set the value to *true*. See [this documentation](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
-3. In a web browser, go to:
-   (For Cortex XSOAR 6.x) `https://*<xsoar_address>*/instance/execute/*<instance_name>*`
-  (For Cortex XSOAR 8 or Cortex XSIAM) `https://ext-<tenant>.crtx.<region>.paloaltonetworks.com/xsoar/instance/execute/<instance-name>`
+1. For Cortex XSOAR 6.x:
+   1. Navigate to **Settings > About > Troubleshooting**.
+   2. In the **Server Configuration** section, verify that the ***instance.execute.external*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add the *instance.execute.external* and set the value to *true*. See [this documentation](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
+2. In a web browser, go to:
+
+   - (For Cortex XSOAR 6.x) `https://*<xsoar_address>*/instance/execute/*<instance_name>*`
+   - (For Cortex XSOAR 8 or Cortex XSIAM) `https://ext-<tenant>.crtx.<region>.paloaltonetworks.com/xsoar/instance/execute/<instance-name>`
 
 
 ### URL Inline Arguments

Packs/EDL/ReleaseNotes/3_2_17.md

@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### Generic Export Indicators Service
+
+- Updated the Readme file for clarification.

Packs/EDL/pack_metadata.json

@@ -2,7 +2,7 @@
     "name": "Generic Export Indicators Service",
     "description": "Use this pack to generate a list based on your Threat Intel Library, and export it to ANY other product in your network, such as your firewall, agent or SIEM. This pack is built for ongoing distribution of indicators from XSOAR to other products in the network, by creating an endpoint with a list of indicators that can be pulled by external vendors.",
     "support": "xsoar",
-    "currentVersion": "3.2.16",
+    "currentVersion": "3.2.17",
     "author": "Cortex XSOAR",
     "url": "https://www.paloaltonetworks.com/cortex",
     "email": "",

Packs/GenericWebhook/Integrations/GenericWebhook/GenericWebhook_description.md

@@ -1,7 +1,8 @@
 We recommend that you use Cortex XSOAR server rerouting when using this integration:
 
+For Cortex XSOAR 6.x only:
 1. Navigate to  **Settings > About > Troubleshooting**.
-2. (For Cortex XSOAR 6.x) In the **Server Configuration** section, verify that the value for the ***instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add *instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>* and set the value to *true*. See the following [reference article](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
+2. In the **Server Configuration** section, verify that the value for the ***instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add *instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>* and set the value to *true*. See the following [reference article](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
 
 **Note**: The ***Listen Port*** needs to be available, which means it has to be unique for each integration instance. It cannot be used by other long-running integrations.
 
@@ -14,4 +15,4 @@ We recommend that you use Cortex XSOAR server rerouting when using this integrat
 
         For example, if the request included in the `Authorization` header the value `Bearer XXX`, then the username should be set to `_header:Authorization` and the password should be set to `Bearer XXX`.
 
-- If you are not using server rerouting as described above, you can configure an HTTPS server by providing a certificate and private key.
+- If you are not using server rerouting as described above, you can configure an HTTPS server by providing a certificate and private key.

Packs/GenericWebhook/Integrations/GenericWebhook/README.md

@@ -17,8 +17,9 @@ The Generic Webhook integration is used to create incidents on event triggers. T
 | store_samples | Store sample events for mapping (Because this is a push-based integration, it cannot fetch sample events in the mapping wizard). | False |
 
 4. Click **Done**.
-5. Navigate to  **Settings > About > Troubleshooting**.
-6. (For Cortex XSOAR 6.x) In the **Server Configuration** section, verify that the value for the ***instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add *instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>* and set the value to *true*. See the following [reference article](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
+5. For Cortex XSOAR 6.x:
+     1. Navigate to  **Settings > About > Troubleshooting**.
+     2. In the **Server Configuration** section, verify that the value for the ***instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add *instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>* and set the value to *true*. See the following [reference article](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
 
 You can now trigger the webhook URL:
 

Packs/GenericWebhook/ReleaseNotes/1_0_27.md

@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### Generic Webhook
+
+- Updated the Readme file for clarification.

Packs/GenericWebhook/pack_metadata.json

@@ -2,7 +2,7 @@
     "name": "Generic Webhook",
     "description": "The Generic Webhook integration is used to create incidents on event triggers.",
     "support": "xsoar",
-    "currentVersion": "1.0.26",
+    "currentVersion": "1.0.27",
     "author": "Cortex XSOAR",
     "url": "https://www.paloaltonetworks.com/cortex",
     "email": "",

Packs/PublishList/Integrations/PublishList/PublishList_description.md

@@ -3,9 +3,9 @@
 - ***List Items on Individual Lines*** - For XSOAR Lists that are comma separated text, this will take all the list items and return them on a separate line, one list item per line.
 
 We recommend that you use Cortex XSOAR server rerouting when using this integration:
-
+For Cortex XSOAR 6.x only:
 1. Navigate to  **Settings > About > Troubleshooting**.
-2. (For Cortex XSOAR 6.x) In the **Server Configuration** section, verify that the value for the ***instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add *instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>* and set the value to *true*. See the following [reference article](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
+2. In the **Server Configuration** section, verify that the value for the ***instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add *instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>* and set the value to *true*. See the following [reference article](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
 
 **Note**: The ***Listen Port*** needs to be available, which means it has to be unique for each integration instance. It cannot be used by other long-running integrations.
 
@@ -18,4 +18,4 @@ We recommend that you use Cortex XSOAR server rerouting when using this integrat
 
         For example, if the request included in the `Authorization` header the value `Bearer XXX`, then the username should be set to `_header:Authorization` and the password should be set to `Bearer XXX`.
 
-- If you are not using server rerouting as described above, you can configure an HTTPS server by providing a certificate and private key.
+- If you are not using server rerouting as described above, you can configure an HTTPS server by providing a certificate and private key.

Packs/PublishList/ReleaseNotes/1_1_2.md

@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### Publish List
+
+- Updated the Readme file for clarification.

Packs/PublishList/pack_metadata.json

@@ -2,7 +2,7 @@
     "name": "Publish List",
     "description": "The Publish List integration is used to publish XSOAR lists for external consumption.",
     "support": "community",
-    "currentVersion": "1.1.1",
+    "currentVersion": "1.1.2",
     "author": "landonc",
     "url": "",
     "email": "",

Packs/SimpleAPIProxy/Integrations/SimpleAPIProxy/SimpleAPIProxy_description.md

@@ -4,8 +4,9 @@
 
 We recommend that you use Cortex XSOAR server rerouting when using this integration:
 
+For Cortex XSOAR 6.x only:
 1. Navigate to  **Settings > About > Troubleshooting**.
-2. (For Cortex XSOAR 6.x) In the **Server Configuration** section, verify that the value for the ***instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add *instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>* and set the value to *true*. See the following [reference article](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
+2. In the **Server Configuration** section, verify that the value for the ***instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add *instance.execute.external.\<INTEGRATION-INSTANCE-NAME\>* and set the value to *true*. See the following [reference article](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke) for further information.
 
 **Note**: The ***Listen Port*** needs to be available, which means it has to be unique for each integration instance. It cannot be used by other long-running integrations.
 
@@ -45,4 +46,4 @@ This is the definition of allowed commands and methods that can be executed via
       "allowed_methods":["GET"]
     }
   ]
-}`
+}`

Packs/SimpleAPIProxy/ReleaseNotes/1_0_2.md

@@ -0,0 +1,6 @@
+
+#### Integrations
+
+##### Simple API Proxy
+
+- Updated the Readme file for clarification.

Packs/SimpleAPIProxy/pack_metadata.json

@@ -2,7 +2,7 @@
     "name": "Simple API Proxy",
     "description": "This pack provides a simple API proxy to restrict privileges or minimize the amount of credentials issued at the API.",
     "support": "community",
-    "currentVersion": "1.0.1",
+    "currentVersion": "1.0.2",
     "author": "thimanshu474",
     "url": "",
     "email": "",

Packs/TAXIIServer/Integrations/TAXII2Server/README.md

@@ -37,7 +37,8 @@ You can add a collection description as is done in *collection1_name*, or enter
 
 To access the TAXII service by instance name, make sure *Instance execute external* is enabled. 
 
-1. In Cortex XSOAR, go to **Settings > About > Troubleshooting**.
+In Cortex XSOAR 6.x:
+1. Navigate to **Settings > About > Troubleshooting**.
 2. In the **Server Configuration** section, verify that the *instance.execute.external* key is set to *true*. If this key does not exist, click **+ Add Server Configuration**, add the *instance.execute.external* and set the value to *true*.
 
 ### How to use HTTPS

Packs/TAXIIServer/Integrations/TAXII2Server/TAXII2Server_description.md

@@ -33,12 +33,13 @@ You can add a collection description as is doen in `collection1_name`, or enter
 ## Access the TAXII Service by Instance Name
 To access the TAXII service by instance name, make sure *Instance execute external* is enabled. 
 
-1. In Cortex XSOAR, go to **Settings > About > Troubleshooting**.
-2. (For Cortex XSOAR 6.x only) In the **Server Configuration** section, verify that the *instance.execute.external* key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add the *instance.execute.external* and set the value to *true*.
-3. You can now trigger the webhook URL:
+1. In Cortex XSOAR 6.x:
+   1. Navigate to **Settings > About > Troubleshooting**.
+   2. In the **Server Configuration** section, verify that the *instance.execute.external* key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add the *instance.execute.external* and set the value to *true*.
+4. Trigger the webhook URL:
 
    - (For Cortex XSOAR 6) In a web browser, go to https://*<xsoar_address>*/instance/execute/*<instance_name>* .
-   -  (For Cortex XSOAR 8 or Cortex XSIAM) `https://ext-<tenant>.crtx.<region>.paloaltonetworks.com/xsoar/instance/execute/<instance-name>`
+   - (For Cortex XSOAR 8 or Cortex XSIAM) `https://ext-<tenant>.crtx.<region>.paloaltonetworks.com/xsoar/instance/execute/<instance-name>`
 
 
 ## How to use HTTPS
@@ -48,4 +49,4 @@ To use HTTPS, a certificate and private key have to be supplied in the integrati
 The integration allows the use of basic authentication in the requests.
 To enable basic authentication, a user and password have to be supplied in the Credentials parameters in the integration configuration.
 
-The server will then authenticate the requests by the `Authorization` header, expecting basic authentication encrypted in base64 to match the given credentials.
+The server will then authenticate the requests by the `Authorization` header, expecting basic authentication encrypted in base64 to match the given credentials.

Packs/TAXIIServer/Integrations/TAXIIServer/README.md

@@ -31,9 +31,10 @@ The collections are defined by a JSON object in the following format:
 
 To access the TAXII service by instance name, make sure ***Instance execute external*** is enabled. 
 
-1. In Cortex XSOAR, go to **Settings > About > Troubleshooting**.
-2. (For Cortex XSOAR 6.x) In the **Server Configuration** section, verify that the ***instance.execute.external*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add the *instance.execute.external* and set the value to *true*.
-3. You can now trigger the webhook URL:
+1. For Cortex XSOAR 6.x:
+   1. Navigate to **Settings > About > Troubleshooting**.
+   2. In the **Server Configuration** section, verify that the ***instance.execute.external*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add the *instance.execute.external* and set the value to *true*.
+2. Trigger the webhook URL:
    - For Cortex XSOAR 6.x: `<CORTEX-XSOAR-URL>/instance/execute/<INTEGRATION-INSTANCE-NAME>`. For example, <https://my.demisto.live/instance/execute/taxiiserver>. Note that the string instance does not refer to the name of your XSOAR instance, but rather is part of the URL.
    -  (For Cortex XSOAR 8 or Cortex XSIAM) `https://ext-<tenant>.crtx.<region>.paloaltonetworks.com/xsoar/instance/execute/<instance-name>`
 

Packs/TAXIIServer/Integrations/TAXIIServer/TAXIIServer_description.md

@@ -27,12 +27,14 @@ The collections are defined by a JSON object in the following format:
 ## Access the TAXII Service by Instance Name
 To access the TAXII service by instance name, make sure ***Instance execute external*** is enabled. 
 
-1. In Cortex XSOAR, go to **Settings > About > Troubleshooting**.
-2. (For Cortex XSOAR 6.x) In the **Server Configuration** section, verify that the ***instance.execute.external*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add the *instance.execute.external* and set the value to *true*.
-3. You can now trigger the webhook URL:
+1. For Cortex XSOAR 6.x:
+   1. Navigate to **Settings > About > Troubleshooting**.
+   2. In the **Server Configuration** section, verify that the ***instance.execute.external*** key is set to *true*. If this key does not exist, click **+ Add Server Configuration** and add the *instance.execute.external* and set the value to *true*.
+2. Trigger the webhook URL:
 
    - For Cortex XSOAR 6.x: **<CORTEX-XSOAR-URL>/instance/execute/<INTEGRATION-INSTANCE-NAME>**. For example, https://my.demisto.live/instance/execute/taxiiserver. Note that the string instance does not refer to the name of your XSOAR instance, but rather is part of the URL.
-(For Cortex XSOAR 8 or Cortex XSIAM) `https://ext-<tenant>.crtx.<region>.paloaltonetworks.com/xsoar/instance/execute/<instance-name>`
+
+   - (For Cortex XSOAR 8 or Cortex XSIAM) `https://ext-<tenant>.crtx.<region>.paloaltonetworks.com/xsoar/instance/execute/<instance-name>`
 
 ## How to use HTTPS
 To use HTTPS, a certificate and private key have to be supplied in the integration configuration. 
@@ -41,4 +43,4 @@ To use HTTPS, a certificate and private key have to be supplied in the integrati
 The integration allows the use of basic authentication in the requests.
 To enable basic authentication, a user and password have to be supplied in the Credentials parameters in the integration configuration.
 
-The server will then authenticate the requests by the `Authorization` header, expecting basic authentication encrypted in base64 to match the given credentials.
+The server will then authenticate the requests by the `Authorization` header, expecting basic authentication encrypted in base64 to match the given credentials.

Packs/TAXIIServer/ReleaseNotes/2_0_52.md

@@ -0,0 +1,9 @@
+
+#### Integrations
+
+##### TAXII Server
+
+- Updated the Readme file for clarification.
+##### TAXII2 Server
+
+- Updated the Readme file for clarification.

Packs/TAXIIServer/pack_metadata.json

@@ -2,7 +2,7 @@
     "name": "TAXII Server",
     "description": "This pack provides TAXII Services for system indicators (Outbound feed).",
     "support": "xsoar",
-    "currentVersion": "2.0.51",
+    "currentVersion": "2.0.52",
     "author": "Cortex XSOAR",
     "url": "https://www.paloaltonetworks.com/cortex",
     "email": "",