Sharing Connection Credentials Using JSON File

Users work on multiple environments and keeping track of credentials for different environments may become difficult. As a Service Administrator, you can simplify this process by creating a connections JSON file and distributing it to your users. A connections JSON file includes Server URL, Client ID, IDCS URL, Scope, and Device Code for all the environments that users work on. It becomes a central resource where you can store, maintain, and distribute connections credentials.

Once users receive the connections JSON file, they can simply load it in Google Sheets using the Load Connections button in the Connect dialog box. Once loaded, users can select the server URL to which they want to connect. The related details are automatically fetched from the JSON file and populated in the other fields. This saves users the effort of manually entering each credential every time they want to connect to a server.

Format of a Connections JSON File

The following is an example of the format of a connections JSON file. This file contains connection credentials for three business process environments.

{
   "https://<SERVICE_URL_1>/HyperionPlanning": {
      "clientId": "<CLIENT_ID_OF_APPLICATION_1>",
      "idcsURL": "https://idcs-<INSTANCE_ID>.identity.oraclecloud.com",
      "scope": "urn:opc:serviceInstanceID=<SERVICE_INSTANCE_ID>urn:opc:resource:consumer::all offline_access",
      "deviceCode": true
   },
   "https://<SERVICE_URL_2>/HyperionPlanning": {
      "clientId": "<CLIENT_ID_OF_APPLICATION_2>",
      "idcsURL": "https://idcs-<INSTANCE_ID>.identity.oraclecloud.com",
      "scope": "urn:opc:serviceInstanceID=<SERVICE_INSTANCE_ID>urn:opc:resource:consumer::all offline_access",
      "deviceCode": false
   },
   "https://<SERVICE_URL_3>/HyperionPlanning": {
      "clientId": "<CLIENT_ID_OF_APPLICATION_3>",
      "idcsURL": "https://idcs-<INSTANCE_ID>.identity.oraclecloud.com",
      "scope": "urn:opc:serviceInstanceID=<SERVICE_INSTANCE_ID>urn:opc:resource:consumer::all offline_access",
      "deviceCode": true
   }
}

When deviceCode is set as true, the Device Code grant type is implemented. While connecting to their business process from Google Sheets, a device code is generated using which users can authenticate.

When deviceCode is set as false, the Authorization code grant type is implemented. While connecting to their business process from Google Sheets, users are prompted to sign in to their business process through an Oracle Cloud Account Sign In page.