FortiSOAR™ provides you with a number of pre-installed connectors or built-ins, such as the SMTP or Database connectors that you can use within FortiSOAR™ playbooks, as a connector step, and perform automated operations. These connectors are bundled and named based on the type of operations the connectors can perform. For example, the Database connector would contain actions that you can perform with respect to the database like querying the database. It is easy to extend and enhance these connectors.
Apart from the FortiSOAR™ Built-in connectors, Fortinet also provides a number of connectors for popular integrations like SIEMs, such as FortiSIEM, Splunk, etc., and Ticketing systems such as Jira. You can see a list of published connectors on the FortiSOAR Connectors Documentation site.
The process of installing, configuring, and using connectors is defined in the Introduction to connectors chapter in the "Connectors Guide", which is part of the FortiSOAR™ documentation or see the Installing a connector and Configuring a connector articles.
FortiSOAR™ Built-in connectors are upgraded by default with a FortiSOAR™ upgrade. Use the Content Hub to upgrade your connectors to the latest version. For more information on the connector store, see the Introduction to connectors chapter and see the FortiSOAR Built-in connectors article.
Important: Before you upgrade your FortiSOAR™ version, it is highly recommended that you take a backup of your FortiSOAR™ Built-in connector's (SSH, IMAP, Database, etc.) configuration since the configuration of your FortiSOAR™ Built-in connectors might be reset if there are changes to the configuration parameters across versions.
Use this connector to set up SMTP for sending system notifications, including requests for resetting passwords, and also for sending emails outside FortiSOAR™. When you configure the SMTP connector, you must ensure that the Mark As Default Configuration option for the configuration that is to be used for sending system notifications is selected.
You can send emails to 30 most recently created FortiSOAR™-teams or users by selecting teams or users from a pre-populated drop-down list using the Recipient Type drop-down list.
If you select Manual Input from the Recipient Type drop-down list, then you can specify a comma-separated list of email addresses, including email addresses of non-FortiSOAR™ users. However, you can also specify the IRI values for users and/or teams, which allows users to reuse team or user information defined in previous playbook steps as Jinja statements.
If you select Team from the Recipient Type drop-down list, then you can send emails by selecting existing FortiSOAR™ teams from the pre-populated To, CC, or BCC multi-select fields, which enables users to dynamically leverage the email ID which has already been provided in a team record, and the email can be sent to all the members of the team at once.
If you select User from the Recipient Type drop-down list, then you can send emails by selecting existing FortiSOAR™ users from the pre-populated To, CC, or BCC multi-select fields, which enables users to dynamically leverage the email ID which has already been provided in a user record. So now you have the ability to interchangeably send emails in multiple formats by specifying a comma-separated list of email addresses or selecting FortiSOAR™-teams or users, or by reusing team or user information defined in previous playbook steps as Jinja statements.
You can pass an existing email template as an input for the email subject and body (content) allowing you to leverage an existing email template and build upon it, thereby, avoiding re-work and ensuring consistency. The Send Email step contains a Body Type drop-down list from which you can choose whether you want to send a plain text email (Plain Text), rich text email (Rich Text), or an email based on a template (Email Template).
If you select Rich Text from the Body Type drop-down list, then in the Content field, you can add formatted content, images, and even custom jinja expressions using Dynamic Values:
If you select Email Template from the Body Type drop-down list, the Email Template drop-down list is displayed, using which you can select the template that you want to use to send the email:
/tmp directory once the playbook completes its execution. Now, when in the "Send Mail" operation the user provides an "Attachment IRI", then the attachment is downloaded from FortiSOAR™ and is saved in the /tmp directory, which will now be deleted once the playbook completes its execution.Contains an updated logo.
Adds support for the 'File' type input in the 'SOAP Call' action. In this case, the WSDL that accepts the input type as 'file' is displayed and the input for the same is accepted as the IRI value of the file or attachment.
This version contains a full-fledged SOAP client that reads WSDL from the configuration and populates the list of actions and all the required/optional inputs from WSDL. Therefore, now you can use the newly added SOAP Call action to integrate SOAP web services with FortiSOAR™. For more information, see the SOAP section.
The SMTP connector could display an error such as "[Error 113] No route to host" on the health check:
Once you view this issue, do the following:
/var/log/mail. You should see the following entry:fatal: parameter inet_interfaces: no local interface found for ::1fatal: parameter inet_interfaces: no local interface found for ::1The issue is restart/start postfix is not working, which is causing the following error:
fatal: parameter inet_interfaces: no local interface found for ::1
Resolution
To resolve this issue, do the following:
/etc/postfix/main.cf file using the vi /etc/postfix/main.cf command, as follows:
inet_interfaces and change it to inet_interfaces = allinet_protocols and change it to inet_protocols = ipv4systemctl restart postfixFortiSOAR™ provides you with a number of pre-installed connectors or built-ins, such as the SMTP or Database connectors that you can use within FortiSOAR™ playbooks, as a connector step, and perform automated operations. These connectors are bundled and named based on the type of operations the connectors can perform. For example, the Database connector would contain actions that you can perform with respect to the database like querying the database. It is easy to extend and enhance these connectors.
Apart from the FortiSOAR™ Built-in connectors, Fortinet also provides a number of connectors for popular integrations like SIEMs, such as FortiSIEM, Splunk, etc., and Ticketing systems such as Jira. You can see a list of published connectors on the FortiSOAR Connectors Documentation site.
The process of installing, configuring, and using connectors is defined in the Introduction to connectors chapter in the "Connectors Guide", which is part of the FortiSOAR™ documentation or see the Installing a connector and Configuring a connector articles.
FortiSOAR™ Built-in connectors are upgraded by default with a FortiSOAR™ upgrade. Use the Content Hub to upgrade your connectors to the latest version. For more information on the connector store, see the Introduction to connectors chapter and see the FortiSOAR Built-in connectors article.
Important: Before you upgrade your FortiSOAR™ version, it is highly recommended that you take a backup of your FortiSOAR™ Built-in connector's (SSH, IMAP, Database, etc.) configuration since the configuration of your FortiSOAR™ Built-in connectors might be reset if there are changes to the configuration parameters across versions.
Use this connector to set up SMTP for sending system notifications, including requests for resetting passwords, and also for sending emails outside FortiSOAR™. When you configure the SMTP connector, you must ensure that the Mark As Default Configuration option for the configuration that is to be used for sending system notifications is selected.
You can send emails to 30 most recently created FortiSOAR™-teams or users by selecting teams or users from a pre-populated drop-down list using the Recipient Type drop-down list.
If you select Manual Input from the Recipient Type drop-down list, then you can specify a comma-separated list of email addresses, including email addresses of non-FortiSOAR™ users. However, you can also specify the IRI values for users and/or teams, which allows users to reuse team or user information defined in previous playbook steps as Jinja statements.
If you select Team from the Recipient Type drop-down list, then you can send emails by selecting existing FortiSOAR™ teams from the pre-populated To, CC, or BCC multi-select fields, which enables users to dynamically leverage the email ID which has already been provided in a team record, and the email can be sent to all the members of the team at once.
If you select User from the Recipient Type drop-down list, then you can send emails by selecting existing FortiSOAR™ users from the pre-populated To, CC, or BCC multi-select fields, which enables users to dynamically leverage the email ID which has already been provided in a user record. So now you have the ability to interchangeably send emails in multiple formats by specifying a comma-separated list of email addresses or selecting FortiSOAR™-teams or users, or by reusing team or user information defined in previous playbook steps as Jinja statements.
You can pass an existing email template as an input for the email subject and body (content) allowing you to leverage an existing email template and build upon it, thereby, avoiding re-work and ensuring consistency. The Send Email step contains a Body Type drop-down list from which you can choose whether you want to send a plain text email (Plain Text), rich text email (Rich Text), or an email based on a template (Email Template).
If you select Rich Text from the Body Type drop-down list, then in the Content field, you can add formatted content, images, and even custom jinja expressions using Dynamic Values:
If you select Email Template from the Body Type drop-down list, the Email Template drop-down list is displayed, using which you can select the template that you want to use to send the email:
/tmp directory once the playbook completes its execution. Now, when in the "Send Mail" operation the user provides an "Attachment IRI", then the attachment is downloaded from FortiSOAR™ and is saved in the /tmp directory, which will now be deleted once the playbook completes its execution.Contains an updated logo.
Adds support for the 'File' type input in the 'SOAP Call' action. In this case, the WSDL that accepts the input type as 'file' is displayed and the input for the same is accepted as the IRI value of the file or attachment.
This version contains a full-fledged SOAP client that reads WSDL from the configuration and populates the list of actions and all the required/optional inputs from WSDL. Therefore, now you can use the newly added SOAP Call action to integrate SOAP web services with FortiSOAR™. For more information, see the SOAP section.
The SMTP connector could display an error such as "[Error 113] No route to host" on the health check:
Once you view this issue, do the following:
/var/log/mail. You should see the following entry:fatal: parameter inet_interfaces: no local interface found for ::1fatal: parameter inet_interfaces: no local interface found for ::1The issue is restart/start postfix is not working, which is causing the following error:
fatal: parameter inet_interfaces: no local interface found for ::1
Resolution
To resolve this issue, do the following:
/etc/postfix/main.cf file using the vi /etc/postfix/main.cf command, as follows:
inet_interfaces and change it to inet_interfaces = allinet_protocols and change it to inet_protocols = ipv4systemctl restart postfix