Integration with Clouds Storages (Google Drive, Dropbox, OneDrive)
Integration HTTP Commander with Clouds Storages allows to interact (edit, upload and download files, folders)
with popular cloud services storage:
Google Drive,
Dropbox,
Microsoft OneDrive,
Box.
Integration with Google Drive allows users of HTTP Commander
create/edit documents in Google Docs, download and upload your files and
folders from the cloud storage Google Drive.
To configure this feature, perform the following steps.
-
Go to the Google Developers Console.
If required, sign in to your Google Account.
Screenshot
-
Create new project (if required).
-
Select the newly created (or existing) project .
Navigation menu -> APIS & Services -> Dashboard.
Then click on the "Select project" (organisation name) right after the Google APIs logo and select your project.
Screenshot
-
The next step is Enable Drive API.
Navigation menu -> APIS & Services -> Library. Type "Drive" in the search box, select Drive API and enable (if it is not enabled yet).
Screenshot
-
Next go to Navigation menu -> APIS & Services -> OAuth consent screen.
First thing to choose here is who will use the project. If you plan to allow use of Google Drive with HTTP Commander only for users of your organisation in the Google (if you have any) , then select "Internal". Otherwise, for public access, select "External". When you select "External", any user with Google account will be able to use integration with Google Drive (and "Edit in Google" feature) in the HTTP Commander.
Second thing to decide is how deep yoou plan to integrate Goolge Drive with the HTTP Commander. HTTP Commander can use Google Drive for:
- Edit office documents in the Google Docs. - In this case only /auth/drive.file scope is required and veriofication of the app is not required.
- Sent files to/from Google Drive. - In this case /auth/drive scope is required and verification of the app is required.
If you do not plan to use integration with Google Drive to exchange files between HTTP Commander and Google Drive, we recommend to add only /auth/drive.file scope.
Please note, that Verification process is required to get rid of the Unverified app" screen only when /auth/drive scope is used.
To get more information about verification process please read this article.
Screenshot
Things you need to fill on the consent screen setting page:
- Application type. Public or internal as described above.
- Application name. Name of the application asking for consent (visible to the end users).
- Application logo. An image on the consent screen that will help users recognize your app(visible to the end users).
- Support email. Email for support (visible to the end users).
-
Scopes for Google APIs. By default you should already have email, profile opendid in the list of scopes.
You will need to add ../auth/drive.file or ../auth/drive scope depending on the integration. So the final list is email, profile, opendid,../auth/drive or email, profile, opendid,../auth/drive.file
-
Authorized domain. Domain of the web server HTTP Commander is running on.
For example: if your opens HTTP Commander site by link http://yourdomain.com/HTCOMNET, set Authorized domain to yourdomain.com
- Application Homepage link. The link top the HTTP Commander installation.
- Application Privacy Policy link. Link to the Privacy Policy. Required for verification
-
Last step is required to get rid of the Unverified app" screen.
Click on the "Submit for verification" button and fill in form in popup window.
Screenshot
-
Next go to Navigation menu -> APIS & Services -> Credentials
and add credentials to your project. Create Credentials -> OAuth client ID
-
Application type - Web application
Name - Any name of the Oauth client in your project. Used only in the Google console. Not visible to the end users.
-
In Authorized JavaScript origins field set your domain of HTTP Commander.
For example: if your opens HTTP Commander site by link http://yourdomain.com/HTCOMNET, set origin http://yourdomain.com/
For Authorized redirect URIs field set empty value.
Press Create button.
Screenshot
-
Copy the value of Client ID.
Screenshot
-
Go to Settings tab of HTTP Commander Admin Panel.
If the hidden settings are not visible, then click Show advanced parameters button on toolbar of Settings tab.
-
In the hidden setting GoogleClientId (section Office)
paste the copied value Client ID.
-
For the parameters EnableDownloadToGoogle,
EnableUploadFromGoogle (section UploadDownload) or-and
EnableGoogleDriveEditor (section Office)
set values to true.
-
After setting the values do not forget to save your HTTP Commander settings
(Save settings button on the toolbar of Settings tab) and restart the application
(Restart application button).
Integration with Dropbox
Integration with Dropbox allows users of HTTP Commander
download and upload your files and folders from the cloud storage Dropbox.
To configure this feature, perform the following steps.
-
Go to the Dropbox App Console.
If required, sign in to your Dropbox Account.
Screenshot
-
Then click Create app button and if necessary, perform the verification email.
Next, check the following sequence settings:
1. Dropbox API
2. Full Dropbox — Access to all files and folders in a user's Dropbox.
2. Then enter the name of the application (for example, HTTPCommander) and click Create app button.
Screenshot
-
Further, on the Settings page open in OAuth 2 section
-
for the Redirect URIs key specify urls to
default.aspx and scripts/clouds/dropbox-callback.html pages of HTTP Commander in lower register (required).
For example. If you open HTTP Commander from url https://yourdomain.com/HTCOMNET, then for Redirect URIs
add https://yourdomain.com/htcomnet/default.aspx and
https://yourdomain.com/htcomnet/scripts/clouds/dropbox-callback.html.
Note! For Redirect URIs parameter url only on https protocol can be specified,
respectively use of Dropbox opportunities possibly if you open HTTP Commander over SSL
that is signed by a valid certification authority (see FAQ: How can I use HTTP Commander with SSL?).
-
For Allow implicit grant choose Allow.
Screenshot
-
On the Branding tab specify Publisher, Description, App website & icons.
This is necessary for production status. Learn more about production status requirements.
Screenshot
-
Go to Settings tab of HTTP Commander Admin Panel.
If the hidden settings are not visible, then click Show advanced parameters button on toolbar of Settings tab.
-
In the hidden setting DropboxConsumerKey (section Office)
paste the value of App Key from Settings tab on page of created application in Dropbox.
-
For the parameters EnableDownloadToDropbox
or-and EnableUploadFromDropbox (section UploadDownload)
set values to true.
-
After setting the values do not forget to save your HTTP Commander settings
(Save settings button on the toolbar of Settings tab) and restart the application
(Restart application button).
-
Then open your HTTP Commander link, which you added to Redirect URIs application settings Dropbox
(for example, https://yourdomain.com/htcomnet/default.aspx), sign in and try to download the file(s)/folder(s)
in your Dropbox storage (use that Dropbox account in which you create an application) using the context menu or toolbar:
Cloud storages → download to... → Dropbox.
-
Next you need to configure user access to his files in Dropbox from HTTP Commander. For this,
go to the Settings tab in your application Dropbox (from Dropbox App Console).
You have two options:
-
Use development status. To do this, click Enable additional users button in line Development users.
But in this case the number of users is limited to a 500 users.
-
Use production status. To do this, click Apply for production button in line Status.
Then fill out the form Request production status, specifying the Web as a Platform
and expect to change the status of.
Screenshot
-
If you set true for EnableDownloadToDropbox,
then in addition, you can customize how the files will be loaded in different sizes to Dropbox (in whole or in chunk):
see parameter MaxFileSizeForDownloadToDropboxEntirely.
Integration with Microsoft OneDrive allows users of HTTP Commander create/edit documents in MS Office Online,
download and upload your files and folders from the cloud storage OneDrive or OneDrive for Business (Office 365).
-
If you plan to use Office 365 (OneDrive for Business), you must have an Office 365 account.
If you do not have an Office 365 account, then you can select
the desired plan and register,
or try the free trial period.
Screenshots
For more info see Get an Office 365 account to access Office 365 APIs.
-
Creating and configuring HTTP Commander application in
App registrations Registration at Azure Portal.
-
To do this, follow the link
and sign in to your OneDrive/Office365 account.
-
On the opened page, click on the button New registration
Screenshot
Note! If you already have configured the application,
then go to step 2.
But before that, check all the settings according to the points below
-
Enter a friendly name for the application, for example 'HttpCommander' and select 'Web app / API' as the Application Type.
-
For the Supported account types, select who will be able to use the application. By default "Accounts in this organizational directory only " is selected.
For integratio nwith personal OneDrive, you will need to select "Accounts in any organizational directory and personal Microsoft accounts".
Note: if option with "Pesonal Microsoft accounts" is not availably at this point, we will configure it in last step.
-
Fore the Redirect URI set the url to the HTTP Commander on your web server https://yourdomain.com/htcomnet/scripts/clouds/onedrive-callback.html
-
Click register to create the application.
Show screenshot
-
In the succeeding page, Find the Application (client) ID value and record it for later. You'll need it to configure Http Commander later.
Show screenshot
-
Next, in the Authentication section make sure the Access tokens check box is selected at the IMPLICIT GRANT section.
Show screenshot
-
Configure Permissions for your application. To that extent, choose the 'API permissions' section and then,
click on Add a permission, then Select an Microsoft Graph API.
Then, click on Delagated Permissions and select following permissions :
-
Files.ReadWrite.All,
-
offline_access,
-
openid,
-
profile,
-
User.Read,
-
Sites.ReadWrite.All, (required for Office 365)
Repeat add permission for the Application Permissions and select following permissions :
-
Files.ReadWrite.All,
-
User.Read.All,
-
Sites.ReadWrite.All (required for Office 365)
Show screenshot
-
Further, you can set up the Branging: logo, link to application, etc..
-
If authentication option "Personal Microsoft accounts" is not available, then we will need to modify application Manifest.
- In your application page, click on "Manifest" to open the inline manifest editor.
- Edit the manifest by locating the "signInAudience" setting, and setting its value to "AzureADandPersonalMicrosoftAccount".
- Save the manifest.
-
Configuring the HTTP Commander.
-
Go to Microsoft Azure Portal.
If you are not already logged in to your OneDrive/Office 365 account, log in.
Choose your HTTP Commander application in the applications list (existing or newly created in the previous step).
-
Copy the value of Application Id (for example 5bbdd707-6688-438d-b38b-4b74ec5eb910).
Screenshot
-
Go to Settings tab of HTTP Commander Admin Panel.
If the hidden settings are not visible, then click Show advanced parameters button on toolbar of Settings tab.
-
In the hidden setting OneDriveApplicationId (section Office)
paste the copied value Application Id.
-
To use the personal OneDrive in HTTP Commander, set the parameter values to true:
EnableDownloadToOneDrive,
EnableUploadFromOneDrive (section UploadDownload)
or-and EnableMsOfficeOnlineEditor (seciton Office).
-
To use the OneDrive for Business (Office 365) in HTTP Commander, set the parameter values to true:
EnableDownloadToOffice365,
EnableUploadFromOffice365 (section UploadDownload)
or-and EnableOffice365Editor (seciton Office).
-
After setting the values do not forget to save your HTTP Commander settings
(Save settings button on the toolbar of Settings tab) and restart the application
(Restart application button).
Note. If in case of log in you receive an error:
We're unable to complete your request
Screenshot
that need to be checked (and to set if not exists) Redirect URIs property.
See Redirect URIs article.
Integration with Box
Integration with Box allows users of HTTP Commander
download and upload your files and
folders from the cloud storage Box.
To configure this feature, perform the following steps.
-
Go to the Box Developers Console (My Apps).
If required, sign in to your Box account.
Screenshot
-
Then click Create New App button, select Custom App and "Next".
Screenshot
-
Select Standard OAuth 2.0 (User Authentication) method and click "Next".
Screenshot
-
Enter a unique name for your app, click Create App and then View Your App.
Screenshots
-
On the page that opens, scroll to the OAuth 2.0 Credentials section.
Screenshot
Copy and specify the Client ID/Secret values for the corresponding parameters in HTTP Commander:
-
Go to Settings tab of HTTP Commander Admin Panel.
If the hidden settings are not visible, then click Show advanced parameters button on toolbar of Settings tab.
-
In the hidden settings BoxClientId,
BoxClientSecret (section Office)
paste the value of Client ID, Client Secret from Box App.
-
For the parameters EnableDownloadToBox
or-and EnableUploadFromBox (section UploadDownload)
set values to true.
-
After setting the values do not forget to save your HTTP Commander settings
(Save settings button on the toolbar of Settings tab) and restart the application
(Restart application button).
-
Then go back to the Box App settings page and enter the following link in the OAuth 2.0 Redirect URI field:
https://yourdomain.com/HTCOMNET/Handlers/BoxOAuth2Handler.ashx
where yourdomain.com/HTCOMNET - path to your HTTP Commander app.
Screenshot
Note! Be sure to use an SSL connection to HTTP Commander
(see FAQ: How can I use HTTP Commander with SSL?).
-
The rest of the settings Box App, leave the default.
Click the Save Changes button to save the settings.
Screenshots
For more info see
Box Custom Apps Setup with OAuth 2.0.