Oracle Identity

Connect Oracle Identity to collect identity & sso evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Oracle Identity:

   1. Sign in to the Oracle Cloud Infrastructure Console as an administrator and go to Identity & Security › Domains.
   2. Click the name of your identity domain, then click Integrated applications.
   3. Click Add application, select Confidential Application, and click Launch workflow.
   4. Enter a name (for example Safeguard reader) and click Submit.
   5. Open the OAuth configuration tab and click Edit OAuth configuration. In Client Configuration, select Configure this application as a client now.
   6. Under Authorization, select only Client credentials as the allowed grant type.
   7. Under Token issuance policy, click Add app roles, then Add roles, select the app role that lets the client read users, click Add, then Submit.
   8. From the Actions menu, select Activate, then Activate Application.
   9. Copy the application's Client ID and Client secret.

   Where to find the other values:

   • Instance URL: Your identity domain's URL; the fetched Oracle pages do not say where it is shown.

   Oracle Identity's public documentation does not cover every step.

   Oracle's docs examples use the User Administrator or Identity Domain Administrator app roles, both broader than read-only; a read-only app role for listing users was not confirmed on the fetched pages.

   Source: docs.oracle.com, docs.oracle.com, checked 2026-10-07.

   The permissions Safeguard needs: read users (confidential application).

2. On Compliance › Connectors, open Oracle Identity, click Connect, choose API token and fill in:

   Field	What to enter
   Instance URL	Required. For example: https://idcs-0123456789abcdef0123456789abcdef.identity.oraclecloud.com
   Client ID	Required.
   Client secret	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Oracle Identity and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Identity & SSO connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks