Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

Debug Logs

For information about managing additional source settings, including debug logging and downloading connector logs, refer to Managing Additional Settings.

Account aggregation succeeds but fewer accounts than expected appear

Issue: Account aggregation completes, but the Accounts tab does not list every IAM user you expect.

Resolution: Confirm that the API key user can list users in the tenancy. The Domains field does not change account aggregation.

Account names include a domain prefix for some users only

Issue: Some accounts show a domain prefix, for example oracleidentitycloudservice/user@example.com, and others show only an email address or user name.

Resolution: This is expected. Users in a non-default identity domain often appear with a domain prefix. Users in the default domain typically appear as an email address or user name only. The display attribute is the OCI user name returned by Identity.

Generative AI Agents are missing from dataset aggregation

Issue: Dataset aggregation completes, but agents do not appear.

Resolution: Confirm that agents exist in a region that hosts Generative AI Agents. If you entered values in Regions or Compartment OCIDs, verify that those values include the region and compartment where the agents run. Confirm that the API key user has the Generative AI Agent permissions listed in Prerequisites.

SMTP credentials are missing from dataset aggregation

Issue: Dataset aggregation completes, and API keys, auth tokens, or customer secret keys appear, but SMTP credentials do not.

Resolution: Grant inspect on the credentials resource type in the tenancy. API keys, auth tokens, and customer secret keys use the existing users permissions. SMTP credentials require a separate credentials policy. For more information, refer to Required Permissions.

Vault secrets are missing from dataset aggregation

Issue: Dataset aggregation completes, but Vault secrets do not appear.

Resolution: Grant inspect and read on secret-family, and optionally inspect on vaults. Do not grant secret-bundles. If you entered values in Regions or Compartment OCIDs, verify that those values include the region and compartment that contain the secrets. Domains do not apply to Vault secrets. For more information, refer to Required Permissions.

Groups are missing after aggregation

Issue: Entitlement aggregation completes, but IAM groups do not appear.

Resolution: Grant inspect groups in the tenancy. Group membership also requires the existing inspect users permission. For more information, refer to Required Permissions.

Issue: Entitlement aggregation completes, but IAM policies do not appear, or a group has no related policies.

Resolution: Grant inspect policies in the tenancy. If Compartment OCIDs is set, confirm that it includes the compartments that contain the policies. Groups are still aggregated when policy access is missing. For more information, refer to Required Permissions.

Hosted applications are missing from dataset aggregation

Issue: Dataset aggregation completes, but hosted applications do not appear.

Resolution: Confirm that the applications exist in a region where OCI Generative AI is offered. If Regions or Compartment OCIDs is set, confirm that those values include the region and compartment that contain the applications. Grant read on generative-ai-hosted-application and generative-ai-hosted-application-iam, and inspect on generative-ai-hosted-deployment. Domains does not apply to hosted applications. For more information, refer to Required Permissions.

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.