Box trading partner

This trading partner exchanges data with Box cloud storage. The MFT Server initiates the connection to the Box cloud storage that is configured for this trading partner. It is assumed that the administrator of the Box cloud storage has provided you with the details needed to set up the Box trading partner - details such as the system's hostname or IP address, port number, username, and password.

 

Adding the Box trading partner

 

In the desired domain, navigate to the AUTOMATION > Trading Partners module. Click on the Add button, or right click anywhere in the grid area and select Add from the pop-up menu. In the Add Trading Partner dialog window, select Box as the Protocol, then click OK. The Add "Box" Trading Partner dialog will appear as depicted in the image below.

 

Before we describe the fields, let's discuss the two ways you can configure Box as a Trading Partner.

  1. Using the FTP/S protocol - This requires you enable FTP/S on your business/enterprise Box account. Access this link for details.

  2. Using the Box API - This option is a bit more involved, and it requires the creation of a Box Application. Expand the text below to learn how to create the Box Application.

 

 

  1. Connect to Box as a developer.

     

  2. Click My Apps, then click Create New App.

     

  3. Click Custom App. A dialog displays titled Create a Custom App.

     

    • On STEP 1 OF 2, enter an app name, description, and purpose. The latter needs to be set along with its corresponding additional fields. The information you enter here does not affect how the MFT Server app functions. Click Next to continue.

       

    • On STEP 2 OF 2, choose Server Authentication (with JWT). Click the Create App button.

       

  4. The details of the new app opens, displaying the Configuration page.

     

    • In the App Access Level section, choose App Access Only.

       

    • In the Application Scopes section, make sure the Write all files and folders stored in Box option is checked.

       

    • In the Add and Manage Public Keys section, click the Generate a Public/Private keypair button. This requires 2 factor authentication (2FA). If you need to enable it, the app will let you know. If 2FA is required, enable it. Click on the Generate a Public/Private keypair button again after 2FA is enabled. A JSON file is automatically downloaded by the browser after a successful generation of the keypair. Keep a copy of the JSON file. This is the JSON file that is needed when configuring a Box Trading partner in MFT Server.

       

  5. Click on the app's Authorization page.

     

    • Click on the Review and Submit button to request authorization.

       

  6. Connect as a Box Admin or have your Box Admin authorize the app.

     

    • Click on Apps, then click on Custom Apps Manager, then click on Server Authentication Apps. Navigate to the app and authorize it.

       

  7. Using the Box Developer console, open the app. There should now be a Service Account Info section. The system randomly generated an email address - known as the Service Account ID. It will look something like: AutomationUser_12345678_abCdeFghIj@boxdevedition.com. Invite this email address as a collaborator on any Box folder that needs to be accessible to the Box Trading Partner.

     

  8. When configuring the Box Trading partner in the MFT Server Manager UI, specify the JSON file as outlined in Step 4.

     

 

clip0476

 

Below you will find a description of the fields.

 

Basic

 

Name - The unique name to assign to this trading partner. Enter a name that best describes the trading partner, as you will be selecting the name when using the partner in MFT Server features that support it.

 

Company - The name of the company that this trading partner represents.

 

E-mail - The primary email address for this trading partner.

 

Authentication

 

  • Service Account Private Key File (JSON) -  If selected, the private key file to use for the connection, accessible to MFT Server.

     

  • Service Account Private Key Data (JSON) - If selected, the contents of the private key file or client-side JSON file to use for the connection. The contents are stored encrypted in the MFT Server configuration database. This is useful when MFT Server is configured for high availability, since the key will be available regardless of which MFT Server server instance is active.

 

Tags

 

Tags - If specified, this is the one or more tags that are used to limit which administrators have access to the network.