Oracle Authorization Connector
Overview
The Dodeca Oracle Authorization Connector provides support for authenticating a user against Oracle services. This allows for integration with Oracle EPM Cloud products such as PBCS/EPBCS, via connectors such as the Dodeca PBCS/EPM Cloud Connector.
The Oracle Authorization Connector is implemented as a native connector and is imported as with any other module into a given Dodeca tenant/application.
Prerequisites
-
An Integrated Application (OAuth application) defined in Oracle Identity Cloud Service (IDCS). The Oracle Authorization Connector needs this in order to obtain a token. See Integrated Application for the steps to create and configure one. The
ClientIDandTenantIDbelow are obtained from this application, as is theServiceInstanceIDrequired by some connectors (such as the PBCS/EPM Cloud Connector).
Getting Started
The connector is available from Applied OLAP. To configure it, follow these steps:
-
Import the Oracle Authorization Connector module: https://downloads.appliedolap.com/products/connectors/Oracle/
-
Restart the Smart Client.
-
Create an Oracle connection using the Authorization_Code grant type.
-
Enter the connection properties below.
-
Commit changes.
Grant Types
The connector supports two OAuth grant types via the GrantType property: Authorization_Code and Device_Code. Authorization_Code is the default and recommended flow, and is what the rest of this document covers. Device_Code (a device-authorization flow for browser-restricted scenarios) is also available but is not detailed here.
Connection Properties
| Property | Requirement | Value |
|---|---|---|
|
Required |
The OAuth grant type. Defaults to |
|
Required |
The alphanumeric segment of the IDCS URL, e.g. for |
|
Required |
Identity -> Domains -> Choose the compartment -> OracleIdentityCloudService domain -> Integrated applications -> Choose the relevant application -> OAuth Configuration tab -> Client ID. |
|
Optional (depending on |
Defaults to |
The TenantID is the alphanumeric segment of the IDCS URL, shown here in the browser address bar while signed into the IDCS Admin console:
The ClientID is shown on the Integrated Application’s OAuth Configuration tab in the IDCS Console:
Once the connection properties are entered, the resulting Oracle connection in Dodeca will resemble the following:
Test Properties
Scopes controls the OAuth scope requested when testing this connection directly. When this connection is used by a consuming connector (such as the PBCS/EPM Cloud Connector, via an Essbase-family connection), the consuming connector computes and overrides Scopes itself, so this can generally be left unset.
| Property | Value |
|---|---|
|
Requested OAuth scopes. Only relevant when testing or using this connection directly, not via a consuming connector. |