Configuration of the G-Suite - Google Drive Connector

Background

Discovery Center needs the SeeUnity server software in order to connect with Google Drive. This should already be setup prior to using this article, but if it is not, please see the article here to complete this installation.

Google configuration

Creating the service account:

The service account is created in the Google APIs Admin Page.  Go to the Google APIs Admin Service accounts section linked here to begin the creation or modification of the account.

At the service account's page, create or review an existing service account to link the connector to your G-Suite domain. 

Under Service Account Details, in order to index all personal drives, you will need to enable Domain Wide Delegation. 

Once created, you can always click in the account under the mentioned link to gather the needed information for the connector.

Acquiring the certificate:

To get the certificate file you will need to click the "Create key" button on the service account details page.  This will generate a new private key and let you download the certificate file which you will need later.

*Please note, this file can only be downloaded once.

Then select “P12” as the key type.

You will then see the download of the file to your computer along with a password provided by Google. Migrate this key to the server that has the SeeUnity CIS software installed as the software will need this key to make the required API calls.  Keep in mind that this file will be utilized by the SeeUnity software and should not be moved, deleted, or modified.

Enabling API Access in G-Suite:

Return to the G-Suite admin page linked here and navigate to Security > Advanced settings > manage API Client Access.

- Enter the Client ID in the Client Name box.
- Enter the following string into the "One or More API Scopes" field and click "Authorize."

https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/drive

Additionally, you must enable access to the following Google APIs:
- Admin Directory API
- Drive API

These can be searched for by following the URL below and enabled on their relevant pages.
https://console.developers.google.com/apis/api/admin.googleapis.com/overview

SeeUnity Server Management Studio Connector Configuration 

1. Launch the SeeUnity Server Management Studio application and expand the "Server Group" node and then navigate into "Local Host" > "Connectors".
2. Right-click on "Data" and select "Add" selecting Google Drive.
3. Under name, put in a name for the connector such as gsuite or mygsuite to be used in Discovery Center.
4. Under Description enter a description for reference.
5. Under Service Account Name enter the service account name from G-Suite.
6. Under Service Account ID enter the Service account ID which is in the email format from G-Suite.
7. Under Private Key file and the path to the private key file.
8. Leave Personal Drives set to all
9. Click "Add."

 
Discovery Center Configuration

Network Map

In the network map, you will create a new location for G-Suite.
The connector type will be google drive and the path will be in the format of:

googledrive://{connectorName}

This {connectorName} value will be what you entered in the name block from the "SeeUnity Server Management Studio Connector Configuration" section of this article. In the example screenshot, this would be googledrive://googledrive

Credential Management

The connector will then need credentials from an account that has access to the G-Suite domain.  This is an additional credential set, and separate from the Service account. Under "System Settings" in Discovery Center, click Credential Management.  From here, create a new credential set using the Username and Password format, and enter the Email Address and Password of the account that has G-Suite access.

Indexing

Finally, go to Indexes, and create a new index using the network location and credentials that relate to this G-Suite instance.

Note that Google Drive does not provide a human-readable hierarchical address for any of its user or team drives or indeed for any object within. Therefore a virtual hierarchy is created by the connector based on the logical structure of the content. You can use the logical structure to start indexes below the top level location if required.