Description This article describes how to troubleshoot and resolve the
'Create/update Alert record failure issue'. Scope FortiSOAR. Solution
When creating or updating a new Alert record either manually or through
a playbook, it may fail with an 'Inte...
Description This article helps to fix the sample playbook issue that
does not come with a connector installation Scope FortiSOAR. Solution
While configuring data ingestion using the connector, it does not show
the sample playbook and fails with the b...
Description This article explains the working of the Threat Intelligence
enrichment playbook - Get File Reputation. Scope FortiSOAR version 7.4.1
or prior. Solution The Enrichment Playbooks are part of the sample
playbooks installed with each Threat ...
Description This article helps to identify and fix the issue that occurs
with the FortiGuard Threat intelligence connector. Scope FortiGuard
Threat intelligence connector - All versions of FortiSOAR prior to
7.4.1. Solution Ingestion fails with the t...
Description This article explains how to fix an issue where the exchange
connector health check does not show correctly or shows as
'disconnected' after upgrading the exchange connector to version 4.1.
Scope Exchange connector version 4.1.0: On-Premi...
Hello @ranjeet Please refer to the below KB, might help in your case as
well.
https://community.fortinet.com/t5/FortiSOAR-Knowledge-Base/Troubleshooting-Tip-Unable-to-create-Alert-records-fails-with/ta-p/279408
Hello @khanchand Thank you for reaching out. You can use the same URL as
shared in the connector guide. This is a complete URL that needs to be
submitted in the browser after replacing the tenant and client ID. It
will return a different URL, use the...
Hello Awni, Kindly refer to the section "Installing or importing and
configuring a connector in FortiSOAR" in the below guide.
https://docs.fortinet.com/document/fortisoar/7.4.1/connectors-guide/929681/introduction-to-connectors
Regards, Ankit Jain
Hello, Could you please test the connectivity via the curl command, does
it shows connected #curl -v https://productapi.fortinet.com If not then
please verify this is allowed in the firewall & Proxy.