> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/integration-instance-configuration-changes/long-running-integrations.md). # Long Running Integrations Some long-running integrations provide internal data via API calls to your third-party software, such as a firewall. During the UAT phase, all long-running integrations are disabled by default. As Cortex XSOAR 6 is the working instance during the UAT phase, we recommend enabling temporarily long running integrations on Cortex XSOAR 8 for testing and then disabling them again until after the switchover date. {% hint style="info" %} ### Important * In Cortex XSOAR 6, a username and password are optional for long-running integrations. In Cortex XSOAR 8, they are required. If you are running a long-running integration on the tenant, you must have a username and password set up for the integration. The username and password can be set per integration, or universally for all long-running integrations on the **Settings & Info** → **Settings** → **Integrations** → **Long Running Integrations** page. * If you have long-running integrations running over a port (not via the instance) and are migrating from Cortex XSOAR 6 On-prem, they will not work in Cortex XSOAR 8 unless you either use an engine or configure the integration to work with the integration instance. {% endhint %} [Forward Requests to Long Running Integrations](/cortex-xsoar-8-saas/configure-cortex-xsoar/integrations/forward-requests-to-long-running-integrations.md) for Cortex XSOAR 8 and then update the URL, username, and password in your third-party software. For Cortex XSOAR Cloud, when configured without an engine, you may need to update long running integrations by changing the URL from `https:///instance/execute//` to `https://ext-.crtx..paloaltonetworks.com/xsoar/instance/execute/`. The following integrations are affected by this change: * O365 Teams (Using Graph API) * Generic Export Indicators Service * Generic Webhook * TAXII Server * TAXII2 Server * XSOAR-Web-Server * PingCastle * Publish List * Simple API Proxy * Syslog v2 * Web File Repository {% hint style="info" %} ### Note * The service is only accessible via URL. * The custom port configured for long-running integrations is ignored. * Custom certificates are not supported. * Authentication (username/password) is mandatory. * Update the client that accesses the integrations to be URL-based only. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/integration-instance-configuration-changes/long-running-integrations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.