Google Drive

Creating your Google Project

Navigate to Google Cloud Console and sign in with your organisational Google account.

Type in the name of your project such as "3Sixty". Then click Create

Enabling APIs

Go to the following link and click select for your project from the drop-down, then click Continue.

Next, click on libraries. Then select APIs.

In the next screen, search for "Google Drive" and click "Google Drive API" from the search results.

Then, click Enable.

Use this method if you wish to authenticate as a specific user to access files and folders.

1. Navigate to the Google Cloud Console and sign in with your organisational Google account,

2. Select your project from the list.

3. Click APIs and Services in the sidebar.

You will now need to create an OAuth Consent Screen that will display when users attempt to authenticate using the app:

Setting up the OAuth Consent Screen

1. Click OAuth consent screen in the sidebar

2. Set user type to External

3. Set your app name. It can be whatever you wish unless...

   1. If you intend to use the Google Vision Text Extractor name the application *3Sixty-VisionTextExtractor/1.0** as that will affect the outcome of the vision tasks (Though those will only work if your project has a linked billing account and billing enabled).

4. Set the support email as the one you used to log in

5. At the bottom, fill in the support email address.

   1. The support email will be the email the user is directed to when they're directed to authorise 3Sixty to transfer data.

6. Click Save and Continue

7. Set up scopes:

Click Add Scope and check

.../auth/drive

Creating OAuth Credentials

1. Return to the APIs and Services Dashboard

2. Click Credentials

3. Click Create Credentials

   

4. Click OAuth Client Id

   

5. On the next screen, select Web Application

6. Give the credentials a name

7. Under Authorised Redirect URIs, add the following

   http://{SIMFLOFY_SERVER}/3sixty-admin/authconn/oauthcb

   Example. If you're running 3Sixty on a local machine

   http://localhost:8080/3sixty-admin/authconn/oauthcb

   Important:  For Manage In Place the domain server has to be public server since Google Drive only supports public server or localhost

    

   Tip:  LOOP BACK IP
   127.0.0.1 will not work, but localhost will

8. Click Create

9. Your new credentials will appear under OAuth 2.0 Client IDs. Click the Download button on the right and retrieve the Client ID and Client Secret from the downloaded json file.

   

Creating your connector in 3Sixty

1. Go to Connections > Authentication

2. Click Create New Authentication Connection

3. Select Google OAuth Connector

4. Fill in your client id and secret, then click Authenticate

5. You will be taken to the OAuth Consent Screen you set up earlier, click Allow

6. You will be returned to 3Sixty, click Save

Completed Checklist

Ensure that you have all the following with your Google project:

• A Google Drive API listed in your dashboard under APIs and Services

• If using Vision Tasks: A Cloud Vision API listed in your dashboard under APIs and Services

• A Web Application OAuth 2.0 Client, listed under Credentials of your project.

  • This should have an authorised redirect URI with the following format: {SIMFLOFY_SERVER}/3sixty-admin/authconn/oauthcb

• A filled out OAuth consent form page with:

  • The ApplicationName " 3Sixty-VisionTextExtractor/1.0 " if using Vision Tasks

  • A support email to be used on the consent screen

  • The email, profile, openid, ../auth/drive

    • If using Vision Tasks ../auth/cloud-vision, ../auth/cloud-platform

• In 3Sixty, a Google OAuth Connector using the secret key and ID from your credentials you created, and the token fields are now populated.

  https://developers.google.com/identity/protocols/oauth2#expiration

  Our app is in testing status, thus refresh token expires in 7 days and need to re-authenticate again!

  Production status apps will not have refresh token expiry!

  

  

  https://stackoverflow.com/questions/71777420/i-want-to-use-google-api-refresh-tokens-forever

Use this method if you wish to create a service user to interact with the data.

Creating The Service Account

1. Go to the APIs and Services Dashboard

2. Click Credentials

3. Click Create Credentials

   

4. Select Service Account

5. You will be asked you to assign roles to the account. Since we need wide-ranging access for now, we should choose Owner. This can be changed later.

   

6. The final screen invites other users to access this service account through their own service account portals. Use as needed for your organization.

   

7. Click DONE. You will be taken back to the service account list for the project.

   Tip:  SERVICE ACCOUNT EMAIL ADDRESS
   Make note of the email address of this user. Any folders or Shared Drives you wish to migrate will need to be shared with this user.

   

8. Click on the three dots under Actions, then click Manage Keys

   

9. Click ADD KEY then Create New Key, then select JSON

   

10. Click Create. You will download a json file to be used in the next step.

1. Go to Connections > Authentication

2. Create a Google JWT Auth Connector

3. Paste the content of that json file into the text box.

4. Click Save.

1. Select Schema Instance from the Navigation Menu or the Dashboard under Discovery

2. Select the new connection button

3. Enter a name for your Discovery Connection

4. Select your connection type from the drop down

5. Click save on the Create Connection form

6. In the edit connection page fill out any addition fields and click save

1. Select integration and click on the new connection button.

2. Enter the name and description of your connection.

3. Select the connection type from the drop down list.

4. Click Save on the Create Connection form.

5. Click Save on the Edit Connection page.

1. Select List Jobs under integration on the navigation menu or the dashboard

2. Click the create job button

3. In the New Job form

   1. Name the job

   2. Select Simple Migration from the job type drop down

   3. Select the Repository Connection

   4. Select the Output connection

   5. Select your Content Service Connection

      (Only required if you will be using Federation)

   6. Click Save to open the Edit Job page

   7. Fill in the configurations for the Repo and Output Configuration tabs

4. Click save to save your new integration job

1. Select Run and Monitor Jobs under Integration in the navigation menu

2. Click the play button next to the job you want to run

3. Click the refresh button to view your completed job status

   (Larger jobs will take longer to run)

if (rd.getACL() != null) {
var newAcl = [];
for (var i in rd.getACL()) {
var acl = rd.getACL()[i];
var split = acl.split('=');
var nRole = ''
if (split[0] != 'AutomationUser_AAAAAAAAAA@boxdevedition.com') {//This is the service user for Box, so we'll skip it
if (split[1] === 'editor') {
nRole = 'writer';
} else if (split[1] === 'owner') {
nRole = 'owner';
} else if (split[1] === 'previewer') {
nRole = 'reader';
} else if (split[1] === 'uploader') {
nRole = 'writer';
} else if (split[1] === 'previewer uploader') {
nRole = 'reader';
} else if (split[1] === 'viewer uploader') {
nRole = 'reader';
} else if (split[1] === 'co_owner') {
nRole = 'writer';
} else {
nRole = 'reader';
}
newAcl.push(split[0] + '=' + nRole);
}
}
rd.setACL(newAcl);
}

1. Click on the task tab in your integration job.

2. Find the task you want to create in the drop down. Tasks are grouped by type. You can also search for the task by name.

3. Select the create task button

4. Fill out the configuration fields. Some tasks do not require configuration.

5. Click Done to save the task to your job.

• checkIn

• checkOut

• createFile

• createFolder

• createVersion

• deleteACL

• deleteFolder

• deleteObjectByID

• deleteVersion

• getACLs

• getFileContent

• getObjectProperties

• getTypes

• getVersionContent

• getVersionProperties

• listFolderItems

• listVersions

• lockDocument

• revertVersion

• setACLs

• unlockDocument

• updateFile

• updateProperties