# FTP Connect

Connect to a FTP Server.

Action available for the following operating systems:

![](/files/-MAlQBZuuTnc6hyzKSVQ)

### Parameters

* **Server** *\<string> -* The IP Address of the FTP Server to connect.
* **Port** *\<numeric> -* The Port of the FTP Server to connect.
* **Username** *\<string> -* The username defined in the FTP Server.
* **Password** *\<string> -* The password defined in the FTP Server for the above **Username**.
* **Mode** *\<unquoted string> -* The mode to the connection to FTP Server. Could be Active, Passive or dynamic.
* **Encryption** *\<unquoted string>*
  * **None** – A normal FTP connection will be used with no encryption
  * **TLS/SSL Explicit** – A connection will be made normally to FTP and a command will be sent to the FTP server explicitly requesting to use any encrypted connection over TLS/SSL sockets. This is normally done on standard port 21.
  * **TLS/SSL Implicit** – A connection will be made to the FTP server and the connection will be immediately encrypted over TLS/SSL sockets before any communication is made. This is normally done on port 990.
  * **SSH FTP Client Password** – A connection will be made using SSHFTP protocol using username/password for authentication. This is normally done on port 22.
  * **SSH FTP Client Password By File** – A connection will be made using SSHFTP protocol using username and a certificate file for authentication. This is normally done on port 22.
  * **SSH FTP Client Certificate By Content**– A connection will be made using SSHFTP protocol using username and a certificate content for authentication. This is normally done on port 22.
* **Certificate File/Content** *\<string> -* The certificate file path or content, according to previous parameter, to use for authentication with the server. The supported certificates are RSA or DSA and should be in OpenSSL format.
* **Finger Print Type***\<unquoted string> -* The server hostkey hash export format (MD5/SHA1/SHA256). This can be used to validate that the server is a known server.
* **Finger Print Target** - The target for the server hostkey hash.
* **Allowed Finger Print List** *\<string> -* If is empty, the server hostkey hash will not be checked, if not empty, this can have a list separated by **CR** of allowed server hostkey hash.

{% hint style="warning" %}
These last four parameters are only for SSH FTP.
{% endhint %}

{% hint style="info" %}
TLS session resumption is currently not supported on Windows 10 client.
{% endhint %}

{% hint style="info" %}
TLS session resumption is currently not supported on Android client.

A non official workaround is available. If you set the **Encryption** parameter to -2 (use the Dynamic option to set this value) this non official workaround will be used.

So option -2 for encryption is equivalent to **TLS/SSL Explicit**, but will use the non official implementation that tries to apply TLS Session Reuse. This may not work in all Android versions and may stop working in the future, so if you use this, be sure to test in the actual devices to confirm that it does work.

If you update Kalipso, be sure to retest this option, since it may be removed in future versions.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.sysdevmobile.com/kalipso5/developing/form/actions/actions-description/group-communications/ftp-connect.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.