Configuration options
SFTPPlus MFT provides flexible configuration options to meet a wide range of operational and administrative needs. The platform supports three main configuration methods:
- Web Console
- command-line tools
- direct configuration INI file editing.
Web Console
SFTPPlus includes an embedded Web Manager console available in every installation. It operates independently and does not require external components such as IIS or a database.
Through the web console, administrators can:
- View and search audit logs
- Manage users, groups, and authentication methods
- Configure file transfer services such as SFTP, FTPS, HTTPS, and WebDAV
- Define automated transfers and file processing rules
- Manage SSH keys, PGP keys, and TLS certificates
- Monitor system status and control active components
The Web Manager can also be used to configure multiple SFTPPlus instances in a clustered or load-balanced environment.
Command-Line Interface (CLI)
All configuration actions available in the web console can also be performed through the admin-shell CLI tool. This tool is included with every SFTPPlus installation and is available for Linux, Windows, and macOS.
Administrators authenticate through the CLI based on their assigned roles, allowing secure, scriptable, and repeatable management operations, suitable for administrators who prefer a text-based workflow.
Configuration File (.INI)
SFTPPlus stores its configuration in a unified .INI file. Any setting available through the Web Console or CLI can also be managed directly in this file.
This approach offers several operational advantages:
- Auditability: Track and compare configuration changes.
- Backup and restore: Save and revert configurations as needed.
- Automation integration: Use the configuration file with deployment tools such as Ansible, CloudFormation, Kubernetes, or OpenShift.
Key Benefits
- Multiple management options: Configure SFTPPlus using a web interface, CLI, or direct file edits.
- Independent operation: The Web Console runs without requiring external servers or databases.
- Consistent configuration model: All management methods share the same underlying configuration structure.
- Automation ready: Easily integrate with infrastructure-as-code and orchestration systems.
- Auditable and recoverable: Maintain configuration history, backups, and restore points.