22
Mule Box Connector Thanh Nguyen

Mule box connector

Embed Size (px)

Citation preview

Mule Box Connector

Thanh Nguyen

Introduction

• The Anypoint Connector for Box is a closed-source, SDK-based connector that provides synchronization of data and automation of processes between Box and third party CRM, CMS, mobile and social applications

Prerequisites

• Anypoint Studio• A Developer account or other valid Box

instance

Hardware and Software Requirements

• Compatibility:Application/Service VersionAnypoint Studio 5.4 or higherMule Runtime EE 3.8.x or higherJava 1.7 or higherBox API 2.0.0Box Java SDK 2.1.1

Install the Connector

• Open Anypoint Studio and go to Help > Install New Software

• Select Anypoint Connectors Update Site - http://repository.mulesoft.org/connectors/releases/3.5.0

• Locate the Box connector.• Click Next and accept the license agreement.• Restart Studio when prompted.

Configure the Connector Global Element

Configure the Connector Global Element

Build a Box IntegrationBuild on Box Platform

Description Integrate Box Partner application or power backend processes using our APIs

Securely access and store content in your custom application using Box Platform

Authentication Mechanism

OAuth 2.0 (3-legged)

OAuth 2.0 with JSON Web Tokens

Users Managed Users Application Users

OAuth 2.0

1. Go to the Global Element tab and click the Create button.

2. Inside the filter textbox enter "Box" and select the option Box: OAuth 2.0 Server to Server.

OAuth 2.0

Field DescriptionClient Id Enter the client_id of the Box

connected app.Client Secret Enter the client_secret for

the connector to access Box.Domain Enter the host of the

callback’s URL as specified in the redirect_uri in Box OAuth2 configuration.

Local Port Enter the port of the callback’s URL.

Path Enter the relative path of the callback’s URL.

OAuth 2.0

OAuth 2.0 Server to Server

1. Go to the Global Element tab and click the Create button.

2. Inside the filter textbox enter "Box" and select the option Box: OAuth 2.0 Server to Server.

OAuth 2.0 Server to Server

• The following credentials are required:Field Description

Client Id Enter the client_id of your application.

Client Secret Enter the client_secret of your application.

Enterprise Id or User Id Enter the enterprise or the user on behalf of the operations will be done.

Private Key Password Enter if the private key of the RSA keypair is encrypted this field has to contain the key password, otherwise can be left blank.

Private Key Path Enter the relative path of the privateKey in the project.

OAuth 2.0 Server to Server

• The following credentials are required:Connection Type Enter the type of connection

which defines the type of token used:•AS_ENTERPRISE_MANAGER•AS_USER.For more information about tokens and token’s constraints check this link.

Encryption Algorithm Enter the algorithm used to verify the JWT signature. Values can only be set to:•RSA_SHA_256•RSA_SHA_384•RSA_SHA_512

OAuth 2.0 Server to Server

• The following credentials are required:

OAuth 2.0 Developer Token

1. Go to the Global Element tab and click the Create button.

2. Inside the filter textbox enter "Box" and select the option Box: OAuth 2.0 Developer Token.

OAuth 2.0 Developer Token

• The following credentials are required:

Connection TypesEnterprise Connection User Connection•Users•Groups

•Folders•Files•Comments•Collaborations•Searches•Tasks

Connector Namespace and Schema

Connector Namespace and Schema

Using the Connector in a Mavenized Mule App

Example Use Case

• This use case describes how to create a Mule application to add a new Folder record in Box using Developer Token Authentication.

Question and answer