Preface
Introduction
- Managed File Transfer General Features
  - Workflow Automation
  - Ad-Hoc File Transfers and Collaboration
- Getting Started
  - Screen Tips
  - Login
Dashboard
Resources
Workflows
Task Reference
Services Overview
Users
Logs and Reports
Encryption
System
Appendix
Glossary Terms
- AES
- Asymmetric
- Asymmetric Cryptology
- Authentication
- Certificate
- Certificate Authority
- CIDR
- Cipher
- Cryptology
- CSV
- Decryption
- Diffie-Hellman/DSS
- Digital Signature
- DSA
- Element
- Encryption
- Fingerprint
- FTP
- FTPS
- Hash Function
- HTTP
- HTTPS
- ICAP
- Icon
- ISO format
- JCE Service Provider
- JDBC drivers
- JKS
- Key
- Key Alias/Key ID
- Key Pair
- Key Store
- MDN
- MMS
- Non-Repudiation
- Passphrase
- PKCS12
- Private Key
- Project
- Public Key
- Public Key Cryptology
- Public Keyring
- RSA
- Run Priority
- SAML
- Secret Key
- Secret Keyring
- Self-Signed Certificate
- SFTP
- Signing
- SMS
- SMTP
- SSH
- SSL
- SSO
- Symmetric
- Symmetric Cryptology
- URL
- Variable
- Verification
- XML

User Guide

10.2.3
- 10.5.3
- 10.5.0
- 10.4.0
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1
- 10.2

Back Next

Quick Start – When no Certificates are required for authentication

Follow the steps below if no certificates are required:

Managed File Transfer

. Specify the parameters (host name, port, user id, password, etc.) for the server. Do not specify any certificates for the resource. This will instruct

Managed File Transfer

to trust this FTPS server no matter what certificate is sent during the SSL handshake.

Add a FTPS task to a

Managed File Transfer

Project and choose the FTPS resource (created in step 1).

You will be able to send and receive files to/from that FTPS server by adding Put or Get elements to the FTPS task in the Project.

Rename Saved Search

Table of Contents

User Guide

User Guide

Quick Start – When no Certificates are required for authentication

Quick Start – When no Certificates are required for authentication