Business Objects 4.3 Authorization Server - Google Drive

by Andrew Calcutt last modified 2023-04-26T14:42:10+00:00


Google Steps

  1. Go to the Credentials page and log in with your google admin user.

  2. Create a new project (or edit an existing one)

  3. In your new project, go to the "OAuth consent screen". Choose type of authentication and click create.

  4. Enter "App information", "App domain", "authorized domains", and "Developer contact information" info

  5. Add Scopes
    1. I checked
      • openid
      • .../auth/

    2. I manually added

  6. Click "Save and Continue" to save the OAuth consent screen settings

  7. Click "Credentials" in the side menu

  8. "Click "Create Credentials" and select "Oauth client ID"

  9. Select "Web Application" and fill out the "Authorized redirect URIs" and click "Create"

  10. Copy down the client id and client secret. Download the json file. The json file also has the client id and client secret, plus other information needed below.

  11. Click OK

  12. Click "Enable APIs & Services" in the side menu

  13. Click the "+Enable APIs & Service" button

  14. Search for "Google Drive API" and enable it

Business Objects Steps

  1. In the CMC, go to the "Applications" section
  2. Right click "Authorization Server Configurations" and choose "Authorization Server Configurations"


  3. Click "Manage -> New Authorization Server"

  4. Enter the items listed below. Most of these values come from you Google API creditials JSON file


    1. Reference Name – Choose a unique random string and enter the same to identify the configuration, to recognize and choose the configuration in different workflows for achieving Authorization-based SSO.

      Google Drive
    2. Description (Optional) – Enter any statement and keywords to describe and quickly identify the configuration out of the list of available configurations.

      ("Blank" in example)

    3. By default, Google OAuth 2.0 can be used both for authentications and authorization. If you want to configure the OpenID Connect for authentications, set the following settings

      1. Enable “OpenID Connect” Authentication 
      2. Issuer URI :
      3. JSON Web Key Sets URI (jwks_uri) :
      4. ID Token Signing Algorithm: RS256

    4. Authorization Endpoint – Enter the URL of the authorization server with which one can get the authorization grant

    5. Token Endpoint – Enter the URL of the authorization server, with which one can request an access token by exchanging the authorization code
    6. Client ID – Enter the name of the Application which is used to register BI Landscape with the Authorization Server

      (This came from the google credential json file)

    7. Client Secret – Enter the specific secret code corresponding to the Application which is used in registering the BI Landscape with the Authorization Server

      (This came from the google credential json file)

    8. Redirect URL – Enter the URL of the BI Landscape endpoint to which the authorization code has to be sent by the Authorization server after successfully validating the authorization. For this purpose, a new endpoint has been introduced in the REST API of the BI Platform, i.e. /oauth2/callback. Hence the URL should be as follows: https://[server]:[port]>/biprws/v1/oauth2/callback.
      • Note:
        • Here the [server] will be the system name hosting the BI landscape application server, where RESTful web services application (biprws) is deployed. And [port] will be the SSL port of the application server.
        • This same url is used for the ""Authorized redirect URIs" url in the Google Steps above.

    9. Revocation Endpoint (Optional) – Enter the URL of the authorization server, with which the application can request the revocation of all previously issued Access Tokens through a specific Refresh Token
    10. Authorization Scope

      openid email

    11. Type of Resource 
      • Google Drive

    12. Custom Parameters (Optional) – Enter any custom parameters required to send while requesting the authorization based on any custom requirements (if needed) of the Authorization Server being configured.
      • Note:
        • The name of the custom parameter should be unique in the configuration
        • At maximum 5 custom parameters are allowed to be configured in any Authorization configuration

  5. Enable Google Drive Destination in Job Server
    1. In the CMC, go to the "Servers" section

    2. Find your "AdaptiveJobServer" server and go to properties.

    3. Under "Destinations" add "Google Drive"

Document Actions