Note the following FTP Adapter restrictions.

• Authenticated encryption with associated data (AEAD) encryption/decryption is not supported.
  Perform the following steps to remove AEAD from your keys on GNU Privacy Guard (GnuPG) 2.4.5. See GnuPG.

  Note:

  Some lower versions of GnuPG may not support these steps.

  1. Open GPG for editing with your key fingerprint.

     gpg --expert --edit-key key_fingerprint

  2. Show the preferences for the key user name and email address.

     gpg> showpref
         [ unknown] (1). Key_User's_Name email@oracle.com
          Cipher: AES256, AES192, AES, 3DES
          AEAD: OCB
          Digest: SHA512, SHA384, SHA256, SHA224, SHA1
          Compression: ZLIB, BZIP2, ZIP, Uncompressed
          Features: MDC, AEAD, Keyserver no-modify

  3. Set your preferences.

     gpg> setpref AES256 AES192 AES SHA512 SHA384 SHA256 SHA224 ZLIB BZIP2 ZIP
         a. Set preference list to:
             Cipher: AES256, AES192, AES, 3DES
             AEAD: 
             Digest: SHA512, SHA384, SHA256, SHA224, SHA1
             Compression: ZLIB, BZIP2, ZIP, Uncompressed
             Features: MDC, Keyserver no-modify

  4. Confirm when prompted to update your preferences.

     Really update the preferences? (y/N) y 

  5. Save your updates.

     gpg> save

• RSA-based PGP keys less than 1024 bits in length are not supported for FTP public key authentication. The recommended length is 2048 bits.
• If you configure the FTP Adapter as an FTP connection or an FTP over SSL connection, file names that have non-ASCII characters are not supported. Any operation such as read, write, list, and others that takes file names or directory paths that have non-ASCII characters does not work. This issue does not impact sFTP connections. See Configure Connection Properties.
• The FTP Adapter does not support TLS resumption.
• The FTP Adapter supports files up to 50 MB in size for schema-based inbound polling using the connectivity agent.
• The FTP Adapter supports files up to 100 MB in size for schema based inbound polling using cloud connectivity through the public gateway.
• The FTP Adapter supports files up to 100 MB file size for schema based inbound polling using cloud connectivity via Public gateway
• The FTP Adapter supports files up to 50 MB in size for schema-based inbound polling using the connectivity agent.
• The FTP Adapter does not support verification on the signed file downloaded from an external FTP server when using a detached signature.
  If a detached signature is used, the signature verification fails with the following exception:

  Signature Verification Failed:Application Error

• The FTP Adapter does not support the IBM FTP server.
• Oracle Integration does not support the form feed char (0xc) feature in the Extensible Markup Language (XML) 1.0 specification.
• You must generate SSH keys in PEM format with the ssh-keygen tool to connect to an on-premises sFTP server. See Generate SSH Keys in PEM Format to Connect to a Public or On-Premises sFTP Server.
• Note the following restrictions when using the connectivity agent with the FTP Adapter:
  • Unzipping is not supported with the Download File operation.
  • When configuring the FTP Adapter to communicate with an sFTP server through the connectivity agent, you must select an algorithm from the SFTP Key Exchange Algorithm field on the Connections page. Do not select the diffie-hellman-group1-sha1 algorithm. This algorithm is not supported with the connectivity agent.
• The FTP Adapter only supports homogeneous arrays in JSON. Heterogeneous arrays in JSON samples and payloads are not supported. An example of a heterogeneous array is as follows:

  {
      "example": [
           "kumar",
          {
              "firstName": ["John"],
          },  
          {
              "length": 100,
              "width": 60,
              "height": 30
          }
  ]
  }

• The FTP Adapter does not support the processing of files from the same folder by two integrations. File deletion causes a conflict. For example, if one integration deletes a file, the second integration cannot find the file to delete, and fails.