So if you are working for a service which regularly requests documents from third parties or external collaborators, CERNBox is particularly useful as you can set up a unique web address which can be given to anyone. Overwriting or deleting the information is also impossible. Once this is done, no one but you will be able to see it. All you need to do is to provide your external clients a unique web address (like LnBpPZvmsoFEEWi) where they can upload any file required. Via this method, files can easily be dropped from any Internet-connected device. Using a web browser, and a secured HTTPS connection, the communication is well encrypted using an established web standard. It is a “file drop” functionality where anyone can “drop” any kind of file into a dedicated folder, which is only accessible to you and to those whom you expressly grant access. This means that it represents the perfect method to allow anyone to upload files intended to be shared with you in a secure and confidential manner. Even better, for receiving documents it allows you to create a unique web address where anyone can deposit a file for you. Rather than using e-mail, why not try CERN IT’s CERNbox service? It encrypts the transmission of documents during the sharing process, avoids the proliferation of copies by offering a single place to deposit a file, and allows revocation of access (useful for example in the case of erroneous attachments or recipients). This means only one thing: alternative communication channels are needed… In v2.4.Do you often find yourself in situations where you would like to share documents with your colleagues, or need to ask people to provide you with documents? Given that many encryption solutions (in particular e-mail encryption) require a certain level of IT skills, such documents invariably end up being requested and sent via e-mail and are therefore unencrypted and hence visible to anyone, as the standard e-mail protocol does not come with any protection. In v2.4.4Īnd earlier, there's no message if the message has been delivered ok, you can check for HTTP status codeĢ00. The Filedop API response is basically a simple OK message that the message has been delivered ok. Interface, there's other protections like authorization tokens that prevents someone from automating anĪttack (the authorization token needs to be fed back to the server. The purpose of the Filedrop api key is authenticate the upload and to provide some protection. The easiest to illustrate is probably with an example, using curl #!/bin/bashįiledrop_url=$filedrop_server/filedrop/filedrop_testįiledrop_api_key=`curl -s -H "Content-Type: text/xml" $filedrop_url | ruby -e 'puts (/\(.*)\/)'`Īttachment_id=`curl -s -X POST -F -user "$filedrop_api_key:x" $filedrop_server/attachments` Please note that it's not possible to use user Filedrops with the API. The Filedrop you want to use with the API, it will list its API key, or you can use the Filedrop Info request If you go to Admin → Filedrop and click on The API key in this instance refers to the Filedrop API key. For instructions how to to upload the file(s), please see the The sending of files is very similar to the sending messages API, with the only real change is that theįiledrop API key is included in the form data. Example using curl with response curl -k -H "Content-Type: text/xml" ĭoc, docx, xls, xlsx, ppt, pptx, png, gif, jpg, jpeg, pdf, zip Validations of those without having to upload a file. (the Filedrop api key) and the file type and file size limitations so that you can implement client side This will respond with details about the Filedrop that can be used to facilitate the Filetransfer The maximum file size that will be accepted by the Filedrop in Megabytes A comma separated list of blocked file extensions, if configured. A comma separated list of accepted filetypes, if configured. The Filedrop API key, this is used to authenticate uploads.Īccepted_filetypes # String. Running a Filedrop Info Request like this: Request URL: /filedrop/_the_filedrop_Īpi_key # String. In order to make client side validation possible when sending through a Filedrop, you can start by Used with unauthenticated uploads and will therefore not need to be authenticated. The Filedrop is the only API call that doesn't use authentication. This API requires LiquidFiles version v2.4.7 or later
0 Comments
Leave a Reply. |