Modern Campus CMS Requirements

FTP/SFTPLink to this section

To publish files, Modern Campus CMS requires an FTP or SFTP account (for example "moderncampuscms") with full rights to create, modify, and rename files and folders in the root folder for the site, which you specify. The account must be able to open multiple simultaneous connections, at least one for each user in Modern Campus CMS.

If you are a SaaS customer, we only support Passive FTP or SFTP. If you are a Self-Hosted customer, you can use Active FTP, Passive FTP, or SFTP.

For Windows instances that wish to use SFTP, we only officially support Bitvise SFTP Server for this purpose. The customer is responsible for the cost, installation, configuration,and maintenance of this product. Modern Campus CMS supports any FTP/SFTP software for Linux and IIS FTP for Windows.

The same FTP or SFTP user created for the Modern Campus CMS application is used by your implementations team during development, unless an alternative is provided. For Windows instances, if using IIS FTP server, select "Unix Style File Listings" instead of DOS, to enable production server file browsing within Modern Campus CMS and designate your Passive FTP ports and enable (whitelist) them in the firewall for use with Modern Campus CMS.

Modern Campus CMS also supports SFTP with the use of public keys. A public key is generated by Modern Campus CMS and obtainable through site settings. This key is provided by the implementations team to be installed on your web server to authenticate the username instead of a password.

FTPS (FTP + SSL) is not supported.

Additional network settings are also required. For a full list of specifications, use our CMS Support Resource Portal to contact us.