Google - Set up OAuth Consent Screen

From 360Works Product Documentation Wiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Overview

Google API Keys are needed for OAuth logins for a number of 360Works products. These keys can also be used to [Access FileMaker Databases using OAuth]. This guide will walk you through setting up an OAuth consent screen and getting Google API Keys.

Generate your own keys

Step 1 Go to https://console.developers.google.com/ . If you do not already have a Google account, you will need to create one. It is recommended that if you are setting this up that you go ahead and create a new account with a username and password that you are comfortable sharing with your users/co-workers

  • Click Create Project.

Step1.png

  • Give the project a name, then click "Create".

GoogleOAuthConsent NewProject.png

  • Now let's set up the OAuth Consent Screen, use the menu to navigate there:

GoogleOAuthConsentScreen OAuthConsent.png

  • For User Type, we will be using "External", which will work for anyone with a Google account, but will show a warning that the app is not verified. If you are a G Suite user, you may choose "Internal" here, and avoid the warning, but this will only work for users inside your G Suite account.
  • Click "Create"

GoogleOAuthConsentScreen SelectUserType.png

  • On the next screen, fill out the following required fields:
  1. App Name (Can be anything)
  2. User Support Email (Use your logged in Gmail address)
  3. Authorized Domains (Use "360Works.com", this is necessary for the OAuth redirect later)
  4. Developer Contact Information (Use your logged in Gmail address)
  • Once all required fields are filled out, click "Save and Continue"

GoogleOAuthConsentScreen AppInformation1.png

GoogleOAuthConsentScreen AppInformation2.png

  • Skip the Scopes for now, we need to enable the API so that we can select them, and we will do that later.
  • Click "Save and Continue"

GoogleOAuthConsentScreen SkipScopes.png

  • Test Users (External accounts only. If you are a GSuite user and selected "Internal" earlier, you may skip this.)
  • Add the Gmail addresses for each user that you will want to be able to authenticate with. For example, if you want to use the Email Plugin to send emails through Gmail, you will need to add the Gmail address you want to send from here. Another example, if you want Zulu to sync with a specific user's Google Calendar, add that user's email address here.
  • Click "Save and Continue"

GoogleOAuthConsentScreen TestUsers.png

  • Summary Screen. Review the details on the summary. If everything looks correct, click the "Back To Dashboard" button.


  • Getting Credentials. After saving the OAuth Consent Screen, navigate to "Credentials" from the menu

GoogleOAuthCredentials Start.png

  • Click "+ Create Credentials", then select "OAuth client ID"

GoogleOAuthCredentials CreateOAuthCreds.png

  • Fill out the form with the following values:
Application Type : Web Application
Name : MyOAuthClient (This can be anything though)
Authorized Redirect URIs : Add both of the following
https://oauth.360works.com/oauth
https://zuluauth.360works.com/zuluauth/auth
  • Click "Create"

GoogleOAuthCredentials CreateClientID.png

  • Once the OAuth Client is created, you will be presented with the Client ID and Client Secret. Save these, as you might not be able to access them later.

GoogleOAuthCredentials ClientCreated.png

  • Now that the client is created, we need to enable the proper APIs and select the proper scopes. See the following pages for product specific steps:
Email_Plugin_-_Google_APIs_and_Scopes
Zulu - Google APIs and Scopes