Skip to main content
Oracle offers no read-only app role that covers everything this connection uses. Give the application the User Administrator app role. It reads and writes users, groups, grants, app roles, apps, dynamic resource groups and password policies. This connector can create, update, delete and activate/deactivate these resources, not only read them. Identity Domain Administrator also works but gives full control of the identity domain. The other administrator roles are not documented to read app roles. One connection manages one identity domain.

Find your Domain URL

The Domain URL is the address of the identity domain you want to connect. The identity domain ID is part of it.

1

Copy the Domain URL

Sign in to the Oracle Cloud Console as an identity domain administrator, then open Identity & Security > Domains.

  • Select the identity domain you want to connect. You may need to change the compartment to find it.
  • Select the Domain information tab.
  • Copy the Domain URL across, as the console shows it.
  • Format: https://{identity domain ID}.identity.oraclecloud.com
  • Example: https://idcs-example.identity.oraclecloud.com
  • The host always ends in .identity.oraclecloud.com.

Register a Confidential Application

The application signs in to your identity domain with its own Client ID and Client Secret, using the Client Credentials grant. It acts as itself, not as a user.

1

Add the application

In the identity domain, select Integrated applications.

  • Select Add application.
  • In the Add application dialog box, select Confidential Application.
  • Select Launch workflow.
2

Name and create the application

On the Add Confidential Application page, enter an application name.

  • Name: StackOne Integration
  • Select Submit.
  • Oracle creates the application in an inactive state and opens its detail page.
3

Choose the Client Credentials grant

On the application detail page, select the OAuth configuration tab.

  • Select Edit OAuth configuration.
  • Under Client configuration, select Configure this application as a client now.
  • Under Authorization, select only Client credentials as the Allowed grant type.
4

Add the app role

At the bottom of the panel, under Token issuance policy, turn on Add app roles.

  • Select Add roles.
  • In the Add app roles panel, select User Administrator.
  • Select Add.
  • Select Submit to save the OAuth configuration.
5

Activate the application

At the top right of the application detail page, open the Actions menu.

  • Select Activate.
  • Confirm the activation.
6

Copy the Client ID and Client Secret

On the OAuth configuration tab, under General information, copy the Client ID across.

  • Next to the Client secret, open the … menu.
  • Select Copy to copy the Client Secret across.
  • Older wizard: some consoles show Next in place of Submit, with the same choices on a Configure OAuth page. Select Next, then Finish, and copy both values across from the Application added dialog box.

Know how long access lasts

Oracle issues access tokens that usually last 3600 seconds (one hour). Oracle documents no expiry for the Client Secret.

Rotate or revoke access

To rotate the Client Secret, regenerate it, then copy the new Client Secret across right away.

  • Open Identity & Security > Domains.
  • Select the identity domain.
  • Select Integrated applications.
  • Select the application.
  • Select the OAuth configuration tab.
  • Select Regenerate secret.
  • Confirm your choice.
  • Copy the new secret across from the New client secret dialog box.
  • Select Close.
  • To revoke access, deactivate the application, then delete it. In Integrated applications, use the Actions menu (three dots) next to the application for both.
1

Connect

  • Click Connect.
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup.
2

Use Actions

Connect an AI platform to the linked account’s actions. See AI Platforms.Other ways to call actions are listed in Protocols & SDKs.