MFT Platform Server Features
MFT Platform Servers have the following features:
- Proprietary protocol to transfer files.
- Initiating a file send or a file receive to a target Platform Server.
- Initiating a directory send or directory receive from a target Platform Server.
- Initiating a file send or file receive to a target Internet Server.
- Initiating a directory send or directory receive from a target Internet Server.
- Support for the following levels of data encryption:
- No data encryption
- AES 256 encryption
- TLS session to negotiate symmetric keys for AES 256 encryption
- Encapsulate all data through TLS tunnel
- Authenticating and passing credentials in multiple ways.
- User profiles: Users can transfer files without knowing the target system credentials.
- Responder profiles: Users can transfer files without providing any credentials to the target server.
- With TLS or Tunnel Mode, you can configure the software to accept only specific certificates.
- When running on z/Linux, Linux, or UNIX, the Platform Server Daemon can run as root or non-root.
- When running on Windows, requests can be validated against the responder profiles or Active Directory.
- When running on z/Linux, Linux, or UNIX requests can be validated against the responder profiles or the password or shadow password files. PAM authentication is also supported.
- Command Center can manage some Platform Server functionality, such as the following functions:
- View completed Platform Server transfers
- View and update node definitions
- View and update profile and responder profile definitions
- Initiate a transfer
- Performing postprocessing actions when a transfer completes. This is discussed in detail later in this document.
- Running a command on a target system.
- Sending an email when a transfer completes, either successfully or unsuccessfully.
- Perform authorization using the security of the UNIX or Windows platform.