> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/connectors/connector-repositories/file-connectors/box/box-authentication-configuration.md). # Box Authentication Configuration This article outlines the process for creating and configuring a Box custom application to obtain the authentication credentials required for establishing a connection with the Box connector. The generated User ID, Client ID, and Client Secret are required to validate and configure the Box connector within the OvalEdge application. The Box connector uses OAuth 2.0–based authentication and requires a properly configured Box custom application with the necessary access permissions and authorization settings. ## Prerequisites Before proceeding with the application setup, ensure the following requirements are met:
PrerequisiteDescription
Box Account AccessAccess to Box with permission to create applications.
Box Developer Console AccessAccess to the Box Developer Console for application creation and configuration.
Box Admin AccessAdministrative privileges to review, authorize, and approve the custom application.
Box Connector Configuration AccessAccess to the OvalEdge application for connector validation and configuration.
{% hint style="warning" %} Administrative approval is required to authorize the custom application before the generated credentials can be used for connector authentication. {% endhint %} ## Create a Box Custom Application ### Step 1: Access the Box Developer Console 1. Sign in to the **Box** account. 2. Navigate to the **Dev Console.**
### Step 2: Create a New Application 1. Click **New App +**.
2. Enter **App Name** and select **Client Credentials Grant**.
3. Click **Create App.**
### Step 3: Configure Permissions 1. Ensure all required permissions shown in the configuration screenshots are enabled. 2. The following permissions and options must be selected: 1. **App Access Level**: Select the radio button **App + Enterprise Access** 2. **Application Scopes**: Enable the checkboxes for 1. Read all files and folders stored in Box 2. Write all files and folders stored in Box
3. **Administrative Actions**: Enable the checkbox **Manage Users.**
4. **Additional Configuration**: Enable the toggle button **Generate User Access Tokens**
3. Click **Save**.
## Retrieve Authentication Credentials ### Step 1: Retrieve User ID 1. Navigate to **Properties** in the App Details panel (right-hand side). 2. Copy the **User ID**.
### Step 2: Retrieve Client ID 1. Navigate to **Access** in the App Details panel (right-hand side). 2. Copy the **Client ID**.
### Step 3: Retrieve Client Secret 1. Click **Fetch Secret**.
2. If **Two-Step Verification** is enabled, complete the verification process.
3. Copy the **Client Secret**.
## Authorization 1. Navigate to **Status** and click **Authorize**.
2. “**Review app authorization**” pop-up will appear. Click **Authorize**.
3. Ensure all permissions are correctly configured before saving. 4. Click **Save**.
{% hint style="info" %} Whenever any changes are made to the application configuration, the application must be re-authorized. {% endhint %} ## Verification 1. Confirm the application status is **Authorized**. 2. Navigate to **Platform Apps.**
3. Verify that the application appears in the list.
{% hint style="warning" %} If the application is not authorized, click Authorize again. {% endhint %} {% hint style="info" %} **Disclaimer** This document is provided for reference purposes only and is subject to change in the future. For the latest information, contact the System Administrator of the system. {% endhint %} *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/release8.2/connectors/connector-repositories/file-connectors/box/box-authentication-configuration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.