Fortinet Document Library

Version:


Table of Contents

6.4.4
Download PDF
Copy Link

FortiSOAR Maintenance Packs

FortiSOAR Maintenance Packs are used to deploy cumulative fixes for a particular released version. This document talks about maintenance packs that will apply to FortiSOAR release 6.4.4.

Maintenance Pack 1

Issues Fixed

  • For deployment of FortiSOAR license where a FortiManager (FMG) acts as an intermediary between the FortiSOAR instance and the FortiGuard Distribution Network (FDN) server, the FortiSOAR license deployment sometimes failed with error:
    FSR-Auth-004: Incomplete contract information is received for the given serial number from FDN/FMG. Contact customer support for more information.
    This issue occurred due to an occasional delay in syncing entitlements to the FMG server. To resolve this issue a one-minute wait and a retry has been added in the license deployment to address the delay. If even after this retry, customers don't receive entitlements, then they need to try to manually deploy the license after 15 minutes of delay.

  • Fixed the issue of playbooks failures caused due to file operations such as creating a file that you want to reuse in a subsequent playbook step not working as expected on a tenant or regional SOC systems that have enabled its remote connector management. For example, playbooks steps such as "File: Create Attachment from File" failed with a File Not Found error when the input to such steps was an output from a previous step of the playbook.

  • Fixed the DNS resolution issue with the Amazon Web Service (AWS) 6.4.4 AMI for Enterprise and Secure Message Exchange. Due to an error with the network service, nameservers were not correctly applied to the FortiSOAR VM and its initial bootstrapping wizard failed to complete.

  • Fixed the intermittent issue that caused the playbooks and direct connector action to fail with the following error:
    'NoneType' object has no attribute 'config_schema'

  • Added important security fixes for Secure Message Exchange.

Steps to install FortiSOAR Maintenance Pack 1

  1. Ensure that update.cybersponse.com is reachable from your VM.
    Note: If your instance can connect to update.cybersponse.com using only a proxy, then ensure that you set the proxy in the /etc/wgetrc, /etc/profile, and yum.conf files. This is required to download the maintenance pack file.
    For example:
    use_proxy=yes
    http_proxy=<proxy_server_ip:port>
    https_proxy=<proxy_server_ip:port>

  2. SSH to your FortiSOAR 6.4.4 VM and log in as a root user.
  3. Download the installer for 6.4.4 maintenance pack 1 using the following command:
    # wget https://update.cybersponse.com/6.4.4/maintenance-packs/install-fortisoar-maintenance-pack-6.4.4-1.bin
  4. To install Maintenance Pack 1 for FortiSOAR 6.4.4, run the following command as a root user:
    # sh install-fortisoar-maintenance-pack-6.4.4-1.bin
    OR
    chmod +x install-fortisoar-maintenance-pack-6.4.4-1.bin
    ./install-fortisoar-maintenance-pack-6.4.4-1.bin

FortiSOAR Maintenance Packs

FortiSOAR Maintenance Packs are used to deploy cumulative fixes for a particular released version. This document talks about maintenance packs that will apply to FortiSOAR release 6.4.4.

Maintenance Pack 1

Issues Fixed

  • For deployment of FortiSOAR license where a FortiManager (FMG) acts as an intermediary between the FortiSOAR instance and the FortiGuard Distribution Network (FDN) server, the FortiSOAR license deployment sometimes failed with error:
    FSR-Auth-004: Incomplete contract information is received for the given serial number from FDN/FMG. Contact customer support for more information.
    This issue occurred due to an occasional delay in syncing entitlements to the FMG server. To resolve this issue a one-minute wait and a retry has been added in the license deployment to address the delay. If even after this retry, customers don't receive entitlements, then they need to try to manually deploy the license after 15 minutes of delay.

  • Fixed the issue of playbooks failures caused due to file operations such as creating a file that you want to reuse in a subsequent playbook step not working as expected on a tenant or regional SOC systems that have enabled its remote connector management. For example, playbooks steps such as "File: Create Attachment from File" failed with a File Not Found error when the input to such steps was an output from a previous step of the playbook.

  • Fixed the DNS resolution issue with the Amazon Web Service (AWS) 6.4.4 AMI for Enterprise and Secure Message Exchange. Due to an error with the network service, nameservers were not correctly applied to the FortiSOAR VM and its initial bootstrapping wizard failed to complete.

  • Fixed the intermittent issue that caused the playbooks and direct connector action to fail with the following error:
    'NoneType' object has no attribute 'config_schema'

  • Added important security fixes for Secure Message Exchange.

Steps to install FortiSOAR Maintenance Pack 1

  1. Ensure that update.cybersponse.com is reachable from your VM.
    Note: If your instance can connect to update.cybersponse.com using only a proxy, then ensure that you set the proxy in the /etc/wgetrc, /etc/profile, and yum.conf files. This is required to download the maintenance pack file.
    For example:
    use_proxy=yes
    http_proxy=<proxy_server_ip:port>
    https_proxy=<proxy_server_ip:port>

  2. SSH to your FortiSOAR 6.4.4 VM and log in as a root user.
  3. Download the installer for 6.4.4 maintenance pack 1 using the following command:
    # wget https://update.cybersponse.com/6.4.4/maintenance-packs/install-fortisoar-maintenance-pack-6.4.4-1.bin
  4. To install Maintenance Pack 1 for FortiSOAR 6.4.4, run the following command as a root user:
    # sh install-fortisoar-maintenance-pack-6.4.4-1.bin
    OR
    chmod +x install-fortisoar-maintenance-pack-6.4.4-1.bin
    ./install-fortisoar-maintenance-pack-6.4.4-1.bin