Troubleshooting Tip: Unable to edit the Connector Configuration on newly deployed FortiSOAR Instances

[bbae]

Description	This article addresses an issue where connector configurations cannot be edited on newly deployed FortiSOAR instances. The problem may occur if Instance A fails and a failover occurs to Instance B after performing the procedure described in Externalization of your FortiSOAR PostgreSQL database
Scope	FortiSOAR v7.5, Connector.
Solution	The issue appears as shown below, where users are unable to edit the connector configuration on the newly deployed FortiSOAR instance B. To resolve this issue, follow the steps below: Verify externalization setup. Ensure that the FortiSOAR instance B was deployed without data migration and that the configuration was completed correctly. Refer to Externalization of your FortiSOAR PostgreSQL database for detailed instructions. Address the connector configuration issue. Follow the guidance in Externalization of your FortiSOAR PostgreSQL database to reinstall all connectors on instance B. This issue occurs because there are no files present at the path /opt/cyops/configs/integrations/connectors_development/<connector-name-version_dev> on Instance B. As a result, the file system is not displayed when attempting to edit the connector. Option 1: Delete the connector from the Create tab in Content Hub, then verify whether the configuration editing issue is resolved. Option 2: Copy the user connector directory from Instance A to Instance B at the following path, and then check whether editing works properly: /opt/cyops/configs/integrations/connectors_development.