# Configuring the Oracle Cloud Infrastructure SaaS Connector

To connect Oracle Cloud Infrastructure (OCI) to Agentic Fabric, you'll generate and enter the API key credentials for an OCI tenancy. This will allow Agentic Fabric to discover OCI generative AI agents, vault secrets, and IAM API key credentials.

!!! important

If your organization has already configured an OCI SaaS source, you can use the existing source for agent discovery. The fields will be prepopulated with the source's information. You can edit these fields to configure a new integration.

## Generating an API Signing Key in Oracle Cloud Infrastructure

Before you begin, ensure your organization has the following in OCI:

- An OCI tenancy with admin access to create IAM users, groups, and policies.

- A dedicated service user for the connector. Avoid using a personal administrator account.

- An IAM group that contains the service user.

**To generate an API signing key:**

1. Follow the [Oracle product documentation](https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#two) to generate an API signing key for the service user.
2. Find and save the values for the [Tenancy Oracle Cloud Identifier](https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#five) (Tenancy OCID), [User Oracle Cloud Identifier](https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#five) (User OCID), [fingerprint](https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#four), and private key. You'll need to enter these values during onboarding.

!!! note

Each OCI SaaS source connects to a single tenancy. Agentic Fabric discovers IAM users and generative AI agent resources within that tenancy.

## Connecting Oracle Cloud Infrastructure to Agentic Fabric

1. Go to the **Connect Sources** step of the Agentic Fabric onboarding experience.
2. Select **OCI SaaS** from the left pane.
3. In the **OCI SaaS** section, complete the following:

- In the **Source Name** field, enter a unique name for the source.
    - In the **Source Owner** field, select the identity who will own the source.
    - In the **Description** field, enter a unique description for the source to distinguish it from similar connections.

4. In the **Configure Authentication** section, complete the following:

- In the **Tenancy OCID** field, enter the OCID of the tenancy that owns the API key user and is the aggregation target. This value must begin with `ocid1.tenancy`.
    - In the **User OCID** field, enter the OCID of the IAM user that owns the API key. This value must begin with `ocid1.user`.
    - In the **Fingerprint** field, paste the key's fingerprint.
    - In the **Private Key** field, enter the PEM-encoded RSA private key for the API key. Do not enter a file path, URL, or Base64 wrapper.

5. Select **Test Connection** to ensure the connection is successful.

6. If the test is successful, select **Aggregate** to run an aggregation for the source. Select **Exit** to skip this step. You can configure aggregations for the source's [datasets](../../../sources/datasets.md#configuring-dataset-aggregations) later in the source's configuration. For information about datasets specific to OCI, refer to the OCI SaaS [connector documentation](https://documentation.sailpoint.com/connectors/saas/oracle_oci/help/saas_connectivity/oracle_oci/datasets.html).

A **Completed** status is now displayed next to the source in the left panel.

7. Choose another connector to configure or select **Continue** to proceed to the next onboarding step.

Configuring the Oracle Cloud Infrastructure SaaS Connector

To connect Oracle Cloud Infrastructure (OCI) to Agentic Fabric, you'll generate and enter the API key credentials for an OCI tenancy. This will allow Agentic Fabric to discover OCI generative AI agents, vault secrets, and IAM API key credentials.

Important

If your organization has already configured an OCI SaaS source, you can use the existing source for agent discovery. The fields will be prepopulated with the source's information. You can edit these fields to configure a new integration.

Generating an API Signing Key in Oracle Cloud Infrastructure

Before you begin, ensure your organization has the following in OCI:

An OCI tenancy with admin access to create IAM users, groups, and policies.
A dedicated service user for the connector. Avoid using a personal administrator account.
An IAM group that contains the service user.

To generate an API signing key:

Follow the Oracle product documentation to generate an API signing key for the service user.
Find and save the values for the Tenancy Oracle Cloud Identifier (Tenancy OCID), User Oracle Cloud Identifier (User OCID), fingerprint, and private key. You'll need to enter these values during onboarding.

Note

Each OCI SaaS source connects to a single tenancy. Agentic Fabric discovers IAM users and generative AI agent resources within that tenancy.

Connecting Oracle Cloud Infrastructure to Agentic Fabric

Go to the Connect Sources step of the Agentic Fabric onboarding experience.
Select OCI SaaS from the left pane.
In the OCI SaaS section, complete the following:
- In the Source Name field, enter a unique name for the source.
- In the Source Owner field, select the identity who will own the source.
- In the Description field, enter a unique description for the source to distinguish it from similar connections.
In the Configure Authentication section, complete the following:
- In the Tenancy OCID field, enter the OCID of the tenancy that owns the API key user and is the aggregation target. This value must begin with ocid1.tenancy.
- In the User OCID field, enter the OCID of the IAM user that owns the API key. This value must begin with ocid1.user.
- In the Fingerprint field, paste the key's fingerprint.
- In the Private Key field, enter the PEM-encoded RSA private key for the API key. Do not enter a file path, URL, or Base64 wrapper.
Select Test Connection to ensure the connection is successful.
If the test is successful, select Aggregate to run an aggregation for the source. Select Exit to skip this step. You can configure aggregations for the source's datasets later in the source's configuration. For information about datasets specific to OCI, refer to the OCI SaaS connector documentation.

A Completed status is now displayed next to the source in the left panel.
Choose another connector to configure or select Continue to proceed to the next onboarding step.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.