---
schema_version: "1"
id: a96694c09cb73a32479e36ea4f2f7b5a4778f744b70e67449c0cee4fc01bcc1f
title: Configure Box Connector 5.3 Using Studio
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/box-connector/latest/box-connector-studio.md
canonical_url: https://docs.mulesoft.com/box-connector/latest/box-connector-studio
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 90e164577ad987132fe0d5ebb4730e757ef260b3f28bf8ec70a63937652971e3
description: MuleSoft Documentation Site
release: "5.3"
latest: true
---
---
product: Box Connector
version: 5.3
is-latest-version: true
---

# Configure Box Connector 5.3 Using Studio

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

You can use this connector in Anypoint Studio by first downloading it from Exchange and configuring
it for your application.

Configure a connector in Anypoint Studio:

1.  Add the connector to your project.

2.  Configure the connector.

3.  Configure an input source for the connector.

## Add the Connector to Your Studio Project

Anypoint Studio provides two ways to add the connector to your Studio project: from the Exchange
button in the Studio taskbar or from the Mule Palette view.

### Add the Connector Using Exchange

1.  In Studio, create a Mule project.

2.  Click the Exchange icon **(X)** in the upper-left of the Studio task bar.

3.  In Exchange, click **Login** and supply your Anypoint Platform username and password.

4.  In Exchange, search for "box".

5.  Select the connector and click **Add to project**.

6.  Follow the prompts to install the connector.

### Add the Connector in Studio

1.  In Studio, create a Mule project.

2.  In the Mule Palette view, click **(X) Search in Exchange**.

3.  In **Add Modules to Project**, type "box" in the search field.

4.  Click this connector’s name in **Available modules**.

5.  Click **Add**.

6.  Click **Finish**.

## Configure the Connector

To use Box Connector in a Mule application, configure a global configuration element that can be
used by as many Box Connectors as you require for your application.

Enter the following information in the **General** tab of the **Global Element Properties** screen
to configure JWT authentication:

<table><colgroup><col> <col></colgroup><thead><tr><th>Parameter</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>Client id</p></div></div></td><td><div><div><p>The client identifier, as assigned by the authorization server when the client application was registered.</p></div></div></td></tr><tr><td><div><div><p>Client secret</p></div></div></td><td><div><div><p>The client application’s client secret.</p></div></div></td></tr><tr><td><div><div><p>Public key id</p></div></div></td><td><div><div><p>The ID of the public key configured in your Box instance to authenticate the application.</p></div></div></td></tr><tr><td><div><div><p>Entity id</p></div></div></td><td><div><div><p>The type of the entity ID: <code>EnterpriseId</code> or <code>UserId</code>.</p></div></div></td></tr><tr><td><div><div><p>Box sub type</p></div></div></td><td><div><div><p>The box subtype: <code>enterprise</code> or <code>user</code>.</p></div></div></td></tr><tr><td><div><div><p>Algorithm</p></div></div></td><td><div><div><p>The RSA encryption algorithm used to encrypt the private key.</p></div></div></td></tr><tr><td><div><div><p>Keystore</p></div></div></td><td><div><div><p>The path to the keystore.</p></div></div></td></tr><tr><td><div><div><p>Keystore type</p></div></div></td><td><div><div><p>The keystore type: <code>JKS</code> or <code>PKCS12</code>.</p></div></div></td></tr><tr><td><div><div><p>Store password</p></div></div></td><td><div><div><p>The password of the keystore.</p></div></div></td></tr><tr><td><div><div><p>Key alias</p></div></div></td><td><div><div><p>The alias that identifies the key.</p></div></div></td></tr><tr><td><div><div><p>Key password</p></div></div></td><td><div><div><p>The key password.</p></div></div></td></tr></tbody></table>

Enter the following information in the **General** tab of the **Global Element Properties** screen
to configure Oauth2security authentication:

<table><colgroup><col> <col></colgroup><thead><tr><th>Parameter</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>Consumer key</p></div></div></td><td><div><div><p>The OAuth consumer key, as registered with the service provider.</p></div></div></td></tr><tr><td><div><div><p>Consumer secret</p></div></div></td><td><div><div><p>The OAuth consumer secret, as registered with the service provider.</p></div></div></td></tr><tr><td><div><div><p>Listener config</p></div></div></td><td><div><div><p>The configuration for the HTTP listener that listens for requests on the access token callback endpoint.</p></div></div></td></tr><tr><td><div><div><p>Callback path</p></div></div></td><td><div><div><p>The path of the access token callback endpoint.</p></div></div></td></tr><tr><td><div><div><p>Authorize path</p></div></div></td><td><div><div><p>The path of the local HTTP endpoint that triggers the OAuth dance.</p></div></div></td></tr></tbody></table>

## Configure an Input Source

Configure an input source for the connector such as a an operation for the Box connector, **HTTP
Listener**, or **Scheduler**. You can put the following operations for the connector in the
**Source** area of the Studio canvas.

**Configuration Name:** The configuration name for the Box connector global element.

**Host:** The host where Box exposes its API.

**Port:** The port where Box services listen for incoming requests.

**Base Path:** The base path of the Box service’s base URI.

**Protocol:** The protocol that Box services follow.

**Client Id:** The client identifier assigned by the authorization server when the client
application was registered.

**Client Secret:** The client application’s client secret.

**Local Callback Path:** The local callback path.

**Local Callback Config:** The HTTP Listener configuration that is used to configure the local
authorization URL.

**External Callback Url:** The redirect URL that is configured by the client application.

**Local Authorization Url:** The local authorization URL that is used to initiate an `OAuth2` dance.

**Authorization Url:** The authorization URL used to request an authorization code.

**Access Token Url:** The access token URL to request for an access token.

## Next Step

After configuring the connector for use in Studio, see the
[Additional Configuration Information](https://docs.mulesoft.com/box-connector/latest/box-connector-config-topics) topic for more configuration
steps.

## See Also

[Salesforce Help](https://help.salesforce.com)