# Configure Google Apps with OAuth 1.0

Note: Support for OAuth 1.0 has been deprecated with the release of MSL 10.1. If you are currently using OAuth 1.0 and upgrade to MSL 10.1 or later software, you should immediately reprogram API access for your application using an OAuth 2.0 Service Account. After you have done this, the OAuth 1.0 tab will be removed from the server manager interface. Note that for new software installations, only OAuth 2.0 is supported.

You can configure the OAuth 1.0 (Open Authentication) settings to grant access to the following Google Apps:

- Google Calendar Data API: Enables integration with Google Calendar in order to display data and synchronize events with MiCollab applications.

- Google Contacts Data API: Enables MiCollab to use the Google Contacts API to create new contacts, edit or delete existing contacts, and query for contacts that match particular criteria.

- Gmail Inbox Feed: Enables MiCollab to use Gmail's Atom feed to request read-only access to a user's Google account for regular updates from news websites, blogs, and/or Gmail.

- Google IMAP and SMTP Access: Enables MiCollab to synchronize NuPoint UM voice mails and email with Google Apps, and allows users to maintain their passwords in one place, Google.

Configuring OAuth is a multi-step process. First you must access Mitel Standard Linux and generate an application manifest for the server. Then you must create a Google Apps project, import the application manifest into it and deploy the project. Finally, you must copy your consumer key and secret from the project back into the MiCollab application on MSL.

## Generate an Application Manifest

An application manifest is an XML file that defines the structure and content of the MiCollab application, including how the application integrates with Google Apps. The file is created in MSL, and its content is dependant on how it has been licensed. Only one file is required per system.

1. Log in to the MSL Server Manager as "admin."

2. In the navigation tree, select Configuration > Google Apps.

3. Select the OAuth 1.0 tab.

4. Under Step 2, click Download Manifest to transfer the manifest file to the local PC.

5. When prompted to Open or Save, click Save.

6. In the file download window that appears, select a location on the local PC to save the file and then click Save.

## Create and Deploy a Google Apps Extension Console Project

The Google Apps extensions console is a tool for configuring an application. In this procedure, you will use it to create a new project, upload your application manifest file, and install the application in your domain.

Note: The following instructions are provided as a guide only. For up-to-date instructions, refer to the Google online help: https://developers.google.com/google-apps/extensions-console/index

Log In to the Google Apps Console

1. Point your browser to http://code.google.com/googleapps/console/a/yourDomainName.

2. Enter the domain administrator Email and password.

Create the Project

1. Click the Create project button or, if you already have other projects, select Create from the drop-down menu.

2. Enter the name for the project (for example, "NuPoint Advanced UM"), and then click Create Project.

Upload the Application Manifest

1. Select the Project tab.

2. Under Manifest, click Upload.

3. Follow the on-screen instructions to select the XML file containing your application manifest (GoogleApps_manifest), and then click Open. The console checks ensure the manifest is valid.

4. When the file passes validation, click Update Project. The Project Overview reappears with a success message.

Install the Application in your Domain

1. Select the Project tab.

2. Click Deploy Application. This begins the process of installing the application described in the manifest file to your domain. The Google Apps Control Panel guides you through a few setup steps, such as granting the application access to your domain's Apps data.

## Copy the Consumer Key and Secret into the Application

This procedure involves copying your OAuth 1 credentials (unique consumer key and matching secret) from the Google Apps extensions console to MSL, which applies the credentials to the MiCollab application.

1. From the Google Apps console, select the Keys tab and copy your credentials:

- Consumer key

- Consumer secret

2. From the MSL Server Manager, under Configuration, click Google Apps

3. Select the OAuth 1.0 tab.

4. Under Step 3, paste your credentials:

- Google Apps Consumer key

- Google Apps Consumer secret

5. Click Save. Your credentials are saved to the MiCollab application, where they are employed immediately.

Note:

- If you regenerate the consumer secret, you must then copy it from the Google Apps project into MSL.

- OAauth 1.0 data is not included in system (MSL) backups. Accordingly, if you perform a backup and restore procedure, you must then re-enter the OAuth 1.0 data in order to restore the Google Apps integration.