Done Authenticated Filedrop

Functionality wise, FTPdrops and Filedrops are the same. Both enable an external user to upload files and these files will be delivered to a predefined local recipient. This is not configurable per external user, it's configurable per FTPdrop/Filedrop. In both cases, you can configure one FTPdrop/Filedrop for each external user you wish to use the FTPdrop/Filedrop if you want. We also have Emaildrops that functionally works the same and anyone that emails to the specific email address, the email will be processed in the same way as a FTPdrop/Filedrop upload will be.

Where they differ is that with FTP, you can set a shared username and password for each FTPdrop where's using Filedrops, anyone who visits the Filedrop can upload files (which in both cases will be delivered to the pre-defined local user per FTPdrop/Filedrop). It is true that anyone that visits the Filedrop can upload files and they will be delivered to the recipient, same as anyone that knows your email can send you emails and attachments. The Filedrop URL is not published anywhere so anyone that wishes to use a Filedrop needs to know the URL so to achieve the same level of authenticity as a shared username/password, you can use a randomized Filedrop URL which makes guessing the URL impossible. You then give each external user their own randomized Filedrop URL and you have achieved the same level of authenticity.

This is not likely to change. The purpose of the Filedrop is to provide a simple way to receive files from external users without username and password. If you wish you external users to authenticate themselves, create accounts for them on your LiquidFiles system in the External Users group and get them to login and send you files that way.

 

If you create a Filedrop with a randomized URL, no one that doesn't have access to the randomized URL will be able to access it. Same as no one that doesn't have access to the username/password cannot access the FTPdrop.