The following integration instances have been changed in Cortex XSOAR 8.
Integration | Description | Change Type | Comments |
|---|---|---|---|
SAML | SAML authentication is part of the Cortex XSOAR platform | Changed | NoteAs a part of the migration, the SAML integration is converted to the SSO settings on the platform level. In Cortex XSOAR 8, you need to Configure Single Sign-On Using SAML 2.0. |
LDAP Authentication | Currently not supported, planned to become a part of the Cortex platform | Removed | |
Microsoft Teams | To use the rerouting configuration in Cortex XSOAR 8, you must use the Microsoft Teams content pack 1.4.43 or higher, and recreate the Demiso Bot in Microsoft Teams. | Changed | For more information about Microsoft Teams and how to reconfigure it, see https://xsoar.pan.dev/docs/reference/integrations/microsoft-teams. |
Currently not supported. | Removed |
Note
If you have a custom (BYOI) integration that receives incoming traffic enabled on a custom port, your environment cannot be migrated at this time.
Reconfigure Integrations
For Cortex XSOAR Cloud, when configured without an engine, you may need to update the following integrations by changing the URL from https://<cortex-xsoar-address>/instance/execute/<instance_name>/ to https://ext-<xsoar-tenant>.crtx.<region>.paloaltonetworks.com/xsoar/instance/execute/<instance-name>.
Publish List: Used to publish XSOAR lists for external consumption.
Simple API Proxy: The Simple API Proxy (Community Contribution) integration provides a simple API proxy to restrict privileges or minimize the amount of credentials issued at the API.
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.
When configured via an engine, both port and URL-based access is supported. No changes need to be made.