Capabilities

• Sync user identities from Box to ConductorOne

• Resources supported:

  • Groups
  • Enterprises

Add a new Box connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

1. In ConductorOne, click Connectors > Add connector.

2. Search for Box and click Add.

3. Choose how to set up the new Box connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

   Do you SSO into Box using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged Box app that was created automatically when you integrated your provider with ConductorOne, rather than creating a new managed app.

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   A Box connector owner must have the following permissions:

   • Connector Administrator or Super Administrator role in ConductorOne
   • Ability to access the Box Developer Console

5. Click Next.

Next steps

• If you are the connector owner, proceed to Configure your Box connector for instructions on integrating Box with ConductorOne.

• If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your Box connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and the ability to access the Box Developer Console must perform this task.

Step 1: Create a new Box custom app

1. Log into the Box Developer Console.

2. Click Create New App and select Custom App.

3. Enter a name for your new app, such as “ConductorOne “, and choose how to categorize the new app.

4. When prompted to choose an authentication method for your new app, select User Authentication (OAuth 2.0).

5. Click Create App.

Step 2: Configure your Box app and gain approval

1. Navigate to your new app’s Configuration tab.

2. In the Application Scopes area, select the following scopes:

   • Manage users
   • Manage groups
   • Manage enterprise properties
   • Grant read resource

3. In the Application Access area, select App + Enterprise Access.

4. Save your changes.

5. Submit your new custom app for approval by a Box Admin. Learn more about this process in the Box developer documentation.

Step 3: Gather Box credentials

1. Navigate to your new app’s Configuration tab and scroll down to the OAuth 2.0 Credentials section of the page.

2. Copy and carefully save the Client ID and Client Secret. We’ll use these in Step 4.

3. Navigate to the app’s General Settings page.

4. Copy and carefully save the Enterprise ID. We’ll use this in Step 4 as well.

Step 4: Add your Box credentials to ConductorOne

1. In ConductorOne, navigate to the Box connector by either:

   • Clicking the Set up connector link in the email you received about configuring the connector.

   • Navigate to Connectors > Box (if there is more than one Box listed, click the one with your name listed as owner and the status Not connected).

2. Find the Settings area of the page and click Edit.

3. Enter the client ID and client secret you looked up in Step 3 into the Client ID and Client secret fields.

4. Enter the enterprise ID you looked up in Step 3 into the Enterprise ID field.

5. Click Save.

6. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Box connector is now pulling access data into ConductorOne.

Configure the Box integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between Box and ConductorOne.

See the ConductorOne Box integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.