Skip to Content

Google OAuth configuration guide for Jitterbit App Builder

Purpose of document

To describe the configuration steps necessary to configure App Builder to use Google as an OIDC/OAuth 2.0 external security provider for user authentication.

Introduction

Configuring external authentication requires setup in both the identity provider and the App Builder instance. In both cases, Administrative rights are required.

Important

The example values provided in this guide are representative, but fictitious, and should not be used in real-world configuration. We are using https://example.zudy.com/App Builder as the instance root in this documentation.

Steps in App Builder

Create a security provider

  1. Sign into App Builder as an Administrator
  2. Navigate to IDE > Security Providers
  3. In the User Authentication section, click + User Authentication to add a new Security Provider

  4. Populate the following values:

    • Name: brief, descriptive name for the Security Provider. Ideally avoid spaces. This becomes part of the App Builder authentication path.
    • Type: External Authentication > OAuth
    • Priority: accept default suggestion, or update per your preference

    • Enabled: Check

      • Authentication Type: OAuth
      • OAuth Grant: Authorization Code

    • OAuth Client Authentication: Basic

    • OAuth Resource Authentication: Bearer
    • Token Owner: User
    • Redirect on Challenge: Check
    • Show on login form: Check
    • User Provisioning: Check
    • Store Claims: Check. This is important when initially setting up and troubleshooting, but can be removed later if desired.

  5. Click Save

Steps in Google Workspace/Google Cloud Platform

Note

Note that you must have Administrator-level access to your organization's Google Workspace account to create a new project, or permissions to create and configure OAuth 2.0 credentials for an existing project.

Create a new project

  1. Go to the Manage resources page in the Google Cloud Console
  2. Sign in as an Administrator if prompted
  3. On the Select organization drop-down list at the top of the page, select the organization in which you want to create a project. If you are a free trial user, skip this step, as this does not apply.
  4. Click Create Project
  5. In the New Project window that appears, enter a project name. A project name can contain only letters, numbers, single quotes, hyphens, spaces, or exclamation points, and must be between 4 and 30 characters. It should be a descriptive and unique name that identifies the project. For example: vinyl-authentication
  6. Select the parent organization in the Organization box
  7. Optionally, select a folder in the Location box. This resource will be the hierarchical parent of the new project.
  8. Click Create

For additional reference on creating projects, please see the Google documentation available at: https://cloud.google.com/resource-manager/docs/creating-managing-projects

  1. After you have created the project, open the Credentials page in the Google API Console. Home > APIs and Services > Credentials
  2. Verify the project name listed in the upper left corner near the logo to make sure that you are using the correct project. Click the drop-down arrow to switch projects, if needed.
  3. Click Create Credentials → OAuth client ID

  4. Unless you have previously set up a consent screen, you will be directed to configure your consent screen first. The consent screen will be presented to the end users when they first access the application (App Builder) using their Google credentials and will prompt them to accept that access to their Google account. If you have already configured a consent screen and scopes, skip to step 29.

    OAuth2.png

    Example configuring consent screen

  5. Click Configure Consent Screen

  6. Select Internal for User Type and click Create
  7. Complete the App Information section as follows:
  8. App Name: Enter the name of the custom app. For example: App Builder Instance. Typically you would specify Dev, QA or Prod, or the purpose of the instance, if different.
  9. User support email: complete with an Administrator's email address or group email address
  10. App logo: optionally upload a file to use as the logo
  11. Complete the App Domain section with the URL of the application home page and a link to your organization's privacy policy and/or terms of service
  12. Under Authorized Domains, add the domain name that the App Builder instance is part of. This may be your own domain or zudy.host. Add multiple domains if applicable.
  13. Enter a support email address for Developer Contact Information
  14. Click Save and Continue

  15. On the Scopes screen identify the information that is being requested about the user, by App Builder. Click Add Scopes and select the three scopes shown in the following screenshot.

    OAuth3.png

    Example configuring Scopes

  16. Click Update

    Note

    Note that these are considered "non-sensitive scopes". No other scopes are required by App Builder.

  17. Click Save and Continue

  18. Review the summary page and click Back to Dashboard
  19. Click Create Credentials → OAuth client ID
  20. Under Application Type, choose Web application
  21. Under Name, type a descriptive label that identifies the application. This value is not used elsewhere. For example: App Builder Instance. Typically you would specify Dev, QA or Prod, or the purpose of the instance, if different.
  22. Under Authorized JavaScript Origins, supply the URI representing the FQDN (fully qualified domain name) of your App Builder instance. Note that this should not include any path information. For example: https://example.zudy.com

  23. The completed screen should look similar to this example:

    OAuth4.png

    Example OAuth client ID configuration

  24. A popup should appear containing your OAuth credentials. These credentials should be kept secret, and will be similar in format to the fictitious examples below. Leave this popup open ready for the next configuration steps.

    • Examples:
    • Your Client ID: 825669012735-hd1oct8l1yeysoslrvtmf6b4gqkl12om.apps.googleusercontent.com
    • Your Client Secret: CRZEXT-zd_Qa_MCZ3rArp5hkRD3B16PPDLN

  25. This completes the steps in Google Workspace/Google Cloud Platform.

Steps in App Builder

Configure security provider properties and claim types

  1. Return to the configuration page for the Service Provider created in steps 1 to 5.

  2. Under the Endpoints section, click + Endpoint and Save the following 3 properties as specified below:

    • AuthorizationEndpoint: use the following value: https://accounts.google.com/o/oauth2/v2/auth
      • Note: this is not an example, it is universal for Google OAuth v2 configuration
    • TokenEndpoint: use the following value: https://www.googleapis.com/oauth2/v4/token
    • UserInfoEndpoint: use the following value: https://openidconnect.googleapis.com/v1/userinfo

  3. Under the Credentials section, click + Credential and Save the following properties as specified below:

    • Type: Client
    • Username: use the Client ID from the previous section, step 32
    • Password: use the Client Secret from the previous section, step 32

  4. Under the Properties section, click + Property and Save the following properties:

    • Scopes: use the 3 scope values shown below. Separate each string with a space:
      • openid
      • https://www.googleapis.com/auth/userinfo.email
      • https://www.googleapis.com/auth/userinfo.profile

  5. Under the Claims section, click + Claim and Save the following Claim Types:

    • Identifier: email (lower case, no spaces)
    • Usage: Name
    • Name: descriptive label. For example: Name

  6. Click Save

  7. Click Create

    • Identifier: email
    • Usage: E-mail Address
    • Name: descriptive label. For example: Email Address

  8. Click Save

    Note

    The E-mail Address usage Claim Type is optional, but will ensure that the Email Address attribute of the App Builder user will be populated when the user signs in to App Builder using the external authentication provider.

  9. This completes the configuration steps in App Builder

Testing

At this point the configuration is ready to test. It is recommended that all tests be performed from new Incognito or Private browser windows, or in an alternate browser.

Testing steps

  1. Navigate to the login page of the App Builder instance and:

    1. Confirm the new authentication method displays appropriately on the login page.
    2. Attempt to sign in with the new authentication method and review the result. (This should be done with a separate login to the one used to administer App Builder.)

  2. If errors are reported, review all the configuration and confirm that elements that are required to match are correct – particularly confirming the Client Secret and Client ID were copied over from Google to App Builder correctly.

  3. If all settings are present and appear correct, but external authentication is still not working, please contact App Builder support.