---
schema_version: "1"
id: 417d2663941b66e8d7efec76d8e0c4611bb72cb742f49d8588727f5f4f3b5e91
title: Box Connector 5.3 Additional Configuration
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/box-connector/latest/box-connector-config-topics.md
canonical_url: https://docs.mulesoft.com/box-connector/latest/box-connector-config-topics
source_site: docs.mulesoft.com
content_type: documentation
content_hash: a06aaf1b8ee4761bedd0483842dffca4a8aa2a27162bb4998b8bca79cfc57957
description: MuleSoft Documentation Site
release: "5.3"
latest: true
---
---
product: Box Connector
version: 5.3
is-latest-version: true
---

# Box Connector 5.3 Additional Configuration

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

To use Box Connector in a Mule app, configure a global Box configuration element to use by as many
Box connectors as needed for your application.

## Configure the Box Connector Global Element

1.  Click the **Global Elements** tab at the base of the canvas.

2.  In the **Global Configuration Elements** screen, click **Create**.

3.  In the **Choose Global Type** wizard, expand Connector Configuration and select
    **Mule-box-connector Config** and click **OK**.  
    In the configuration screen for `OAUTH 2.0` with Authorization Code, grant type displays. This
    is the only configuration that Box Connector supports.

4.  Configure the properties as described here.

    <table><colgroup><col> <col></colgroup><thead><tr><th>Parameter</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p><code>clientId</code></p></div></div></td><td><div><div><p>Specifies 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><code>clientSecret</code></p></div></div></td><td><div><div><p>Specifies the client application’s client secret.</p></div></div></td></tr><tr><td><div><div><p><code>host</code></p></div></div></td><td><div><div><p>The host where Box exposes its API.</p></div></div></td></tr><tr><td><div><div><p><code>port</code></p></div></div></td><td><div><div><p>The port where Box services listen for incoming requests. Default: 443</p></div></div></td></tr><tr><td><div><div><p><code>basePath</code></p></div></div></td><td><div><div><p>The base path for the Box services' base URI.</p></div></div></td></tr><tr><td><div><div><p><code>protocol</code></p></div></div></td><td><div><div><p>The protocol which Box services follow. Default: HTTPS</p></div></div></td></tr><tr><td><div><div><p><code>localCallbackPath</code></p></div></div></td><td><div><div><p>The local callback path. Default: /callback</p></div></div></td></tr><tr><td><div><div><p><code>localCallbackConfig</code></p></div></div></td><td><div><div><p>The HTTP Listener configuration that is used to configure the local authorization URL.</p></div></div></td></tr><tr><td><div><div><p><code>externalCallbackUrl</code></p></div></div></td><td><div><div><p>The redirect URL that is configured in the client application.</p></div></div></td></tr><tr><td><div><div><p><code>localAuthorizationUrl</code></p></div></div></td><td><div><div><p>Local authorization URL that is used to initiate an <code>OAuth2</code> dance.</p></div></div></td></tr><tr><td><div><div><p><code>authorizationUrl</code></p></div></div></td><td><div><div><p>The authorization URL to request for an authorization code.</p></div></div></td></tr><tr><td><div><div><p><code>accessTokenUrl</code></p></div></div></td><td><div><div><p>Specifies the URL for requesting an access token.</p></div></div></td></tr></tbody></table>

    In the `OAUTH 2.0` configuration screen, the placeholder values refer to a configuration file
    `mule-artifact.properties` placed in the `src/main/resources` folder of your project.

    You can either enter your credentials into the global configuration properties, or reference a
    configuration file that contains these values.

    > [!NOTE] Use a configuration file for simpler maintenance and better reusability of your
    > project. Keeping these values in a separate file is useful if you need to deploy to different
    > environments where your access credentials are different, such as production, development, and
    > QA.

5.  Click **OK**.

## JWT Authentication

Authenticate your application directly to Box using a JSON Web Token (JWT).

The following steps describe how to configure Box Connector using JWT:

- [Create an App](#create-an-app)

- [Generate a Keypair](#generate-a-keypair)

- [Export and Add the Public Key](#export-and-add)

### Create an App

1.  Go to the [Developer Console](https://app.box.com/developers/console).

2.  Select **Create New App**.

3.  Select **Custom App** for the type of application.

4.  Select **Server Authentication (with JWT)** for the type of authentication.

5.  Provide a name for the application.

6.  Click **Create App**.

![Custom app selection](/mulesoft/current/en-us/box-connector/latest/_images/box-custom-app-select.png)

### Generate a Keypair

1.  Download [KeyStore Explorer](https://keystore-explorer.org).

2.  Open the application and select **Create a new KeyStore**.

3.  Select **JKS**.

4.  Click **OK**.

5.  Click **Save**.

    ![Create new JKS KeyStore selection](/mulesoft/current/en-us/box-connector/latest/_images/keystore-jks.png)

6.  Click on **Tools** and select **Generate Key Pair**.

7.  Select **RSA** with a key size of 2048.

    ![RSA with a key size of 2048 selection](/mulesoft/current/en-us/box-connector/latest/_images/rsa-2048.png)

8.  Click **OK** to prompt the **Generate Key Pair Certificate** dialog box to appear.

9.  Accept the default settings.

    ![Generate Key Pair Certificate dialog box](/mulesoft/current/en-us/box-connector/latest/_images/generate-keypair-certificate.png)

10. Click on the **Name** icon and add the following information:

    - **Common Name (CN)**: mulesoft

    - **Organization Unit (OU)**: mulesoft

    - **Organization Name (O)**: mulesoft

    - **Locality Name (L)**: mulesoft

    - **State Name (ST)**: mulesoft

    - **Country (C)**: CA

11. Click **OK**.

    ![Information added to the Name icon dialog box](/mulesoft/current/en-us/box-connector/latest/_images/name.png)

12. Click **Save** to prompt the **New Key Pair Entry Alias** dialog box to appear.

13. Enter **mulesoft** as the alias.

    ![Added mulesoft alias to New Key Pair Entry Alias dialog box](/mulesoft/current/en-us/box-connector/latest/_images/keypair-alias.png)

14. Click **OK** to prompt the **New Key Pair Entry Password** dialog box to appear.

15. Enter a new password.

    ![Added password to New Key Pair Entry Password dialog box](/mulesoft/current/en-us/box-connector/latest/_images/keypair-password.png)

16. Click **OK** to successfully generate your keypair.

### Export and Add the Public Key

1.  Right-click on the generated keypair and navigate to **Export** > **Export Public Key**.

    ![Navigation for Export Public Key](/mulesoft/current/en-us/box-connector/latest/_images/export-public-key.png)

2.  Save your keystore and set a password.

3.  Open the exported public key in the editor and copy all the content.

4.  Go to the [Developer Console](https://app.box.com/developers/console).

5.  Go to the **Configuration** tab and scroll down to the **Add and Manage Public Keys** section.

6.  Click **Add a Public Key** and paste all the copied content.

    ![Add Public Key button](/mulesoft/current/en-us/box-connector/latest/_images/add-public-key.png)

7.  Click **Verify and Save**.

8.  After successful verification, you will receive the **Public key id**.  
    You can also find other properties that depend on your application, such as **Entity id** and
    **Box sub type**, in the Developer Console on the **General Settings** tab in the **App Info**
    section and add them to the Studio configuration.

![Studio configuration](/mulesoft/current/en-us/box-connector/latest/_images/studio-config.png)

## Next

Now that you have completed configuration, you can try out the Box Connector
[Examples](https://docs.mulesoft.com/box-connector/latest/box-connector-examples).

## See Also

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