Box Additional Configuration - Mule 4
To use the Box connector in a Mule app, configure a global Box configuration element to use by as many Box connectors as needed for your application.
Click the Global Elements tab at the base of the canvas.
In the Global Configuration Elements screen, click Create.
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.0with Authorization Code, grant type displays. This is the only configuration that Box connector supports.
Configure the properties as described here.
Specifies the client identifier as assigned by the authorization server when the client application was registered.
Specifies the client application’s client secret.
The host where Box exposes its API.
The port where Box services listen for incoming requests. Default: 443
The base path for the Box services' base URI.
The protocol which Box services follow. Default: HTTPS
The local callback path. Default: /callback
The HTTP Listener configuration that is used to configure the local authorization URL.
The redirect URL that is configured in the client application.
Local authorization URL that is used to initiate an
The authorization URL to request for an authorization code.
Specifies the URL for requesting an access token.
OAUTH 2.0configuration screen, the placeholder values refer to a configuration file
mule-artifact.propertiesplaced in the
src/main/resourcesfolder of your project.
You can either enter your credentials into the global configuration properties, or reference a configuration file that contains these values.
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.
Now that you have completed configuration, you can try out the Box Connector Examples.