Connect Box

This page describes how to connect Box to Agentspace. The connector supports both data ingestion and federated search. See the section for the approach you plan to use:

• Connect Box (data ingestion)
• Connect Federated Search with Box

Connect Box (data ingestion)

Use the following procedure to sync data from Box to Agentspace.

After you set up your data source and import data the first time, the data store syncs data from that source at a frequency that you select during setup.

Before you begin

Before setting up your connection:

1. You must have administrator access to the Box instance, with two-factor authentication enabled. All the set up instructions can only be performed from the administrator account.

2. Set up access control for your data source. For information about setting up access control, see Use data source access control .

3. Read Setup with JWT in the Box documentation for an overview of the setup, with screenshots.

Create a Box app

1. Sign in to the Box Developer Console with your administrator account.
2. Click Create platform app.
3. Select App typeas Custom app.
4. Enter the App name.
5. Set the following properties:
   1. Purpose:Integration
   2. Categories:AI
   3. External system:Google Cloud Agentspace
6. Select Authentication methodas Server authentication (with JWT).
7. Click Create app.

Configure the Box app

1. In the Box Developer Console , choose the Platform appand then go to the Configurationtab.
2. In the App access levelsection, select App + Enterprise access.

3. In the Application scopessection, select the following scopes:

   1. Read all files and folders stored in Box
   2. Write all files and folders stored in Box
   3. Manage users
   4. Manage groups
   5. Manage enterprise properties

4. In the Advanced featuressection, select Make API calls using the as-user header.

5. In the Add and manage public keyssection, click Generate a public/private keypair.

   1. The public keyis automatically uploaded to the console with an ID. This ID is used when creating a connection.
   2. You can download a configuration file with the private key and passphrase. Make sure to keep this file for later use.
   3. Optionally, to generate your own key, see the Box keypair setup guide .

6. Click Save changes.

Authorize the Box app

1. In the Box Developer Console , choose the Platform appand then go to the Authorizationtab.
2. Click Review and submit.
3. In the Review app authorization submissiondialog, click Submit.
4. Sign in to the Box admin platform apps manager with your administrator account.
5. Choose the Platform appthat you have configured.
6. Click the three dots ( ...) in the corresponding row.
7. Select Authorize appfrom the drop-down list.
8. In the Authorize appdialog, click Authorizeto complete the authorization process.

Have the following Box authentication information ready:

• Enterprise ID: Obtain it from the General settingstab.
• Client IDand Client secret: Obtain it from the Configurationtab under OAuth 2.0 credentials.
• Private key, Key ID, and Passphrase: These parameters were already generated and downloaded to a local file from the Configurationtab under Add and manage public keyswhile configuring the app.

Create a Box connector

Next steps

• To attach your data store to an app, create an app and select your data store following the steps in Create a search app .

• To preview how your search results appear after your app and data store are set up, see Get search results .

• To enable alerts for the data store, see Configure alerts for third-party data stores .

Connect Federated Search with Box

Use the following procedure to search through your Box account using federated search.

About federated search

With data federation, Agentspace directly retrieves information from the third-party data sources using APIs, instead of copying the data into Agentspace. Using this approach, you can access external data sources immediately, without waiting for ingestion.

Before you begin

Before creating a Box data store in Agentspace, you must register an OAuth 2.0 application in the Box Developer Console.

To register the application, do the following:

1. Sign in to the Box Developer Console with your administrator account.

2. Click Create Platform App.

   

3. Click Custom App.

4. Fill out the required fields.

   

5. Select User Authentication (OAuth 2.0).

   

6. Click Create App.

7. Copy the Client IDand Client Secret. These are required to create a federated search data store with Box in Agentspace.

   

8. In the OAuth 2.0 Redirect URIssection, add the following redirect URIs:

   • https://vertexaisearch.cloud.google.com/console/oauth/default_oauth.html
   • https://vertexaisearch.cloud.google.com/oauth-redirect

   

9. Select the following application scopes:

   • Read all files and folders stored in Box
   • Write all files and folders stored in Box

   

10. Click Save Changes.

Create a federated search connector with Box

User authorization

After creating a federated search data store, you can see it listed as one of the data sources in your source management panel. If you haven't previously authorized Agentspace, then you can't select the data source. Instead, an Authorizebutton appears next to it.

To initiate the authorization flow:

1. Click Authorize. You are redirected to the Box authorization server.

   

2. Sign in to your Box account.

3. Click Grant access. After granting access, you are redirected back to Agentspace to complete the authorization flow.

   Agentspace obtains the access_token , and uses it to access the 3P search.

Query execution

When you enter a search query:

• If Box federated search is authorized, Agentspace sends the query to the Box API.
• Agentspace blends the results with those from other sources and displays them.

Data handling

When using third-party federated search, your query string is sent to the third-party search backend. These third parties may associate queries with your identity. If multiple federated search data sources are enabled, the query may be sent to all of them.

Once the data reaches the third-party system, it is governed by that system's Terms of Service and privacy policies (not by Google Cloud's terms).