# SailPoint Oracle Database Connector Documentation > Oracle Database Connector Documentation # Documentation # Connecting SailPoint and Oracle Database To connect SailPoint with Oracle Database, perform the following tasks: ## Adding the Source in SailPoint To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs. > [!IMPORTANT] > > By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration. **To configure a new source:** 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Configure**. 5. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 6. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters. 7. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](). 8. Under **Connection Type**, select **Direct Connection** or **Flat File**. - **Direct Connection** - A direct connection fetches data from the **Virtual Appliance Cluster** you choose as the application connector for the source. A direct connection configuration allows for real-time updates. For more information about configuring and deploying virtual appliances, refer to the [Virtual Appliance Reference Guide](). - **Flat File** - Select the flat file if no connector is available, or if another system restricts the connection. This option allows only reading and aggregating data as a generic/delimited application. Provisioning activity is unsupported, and additional configuration pages like connection settings and aggregation settings are unavailable. 9. If you selected **Direct Connection**, in **Virtual Appliance Cluster**, select the virtual appliance cluster that will be used as the application connector for the source. 10. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 11. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](). 12. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## Base Configuration Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary. 1. Enter a unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 3. In the **Virtual Appliance Cluster** dropdown list, select the virtual appliance to use when communicating with your organization's systems. For more information, refer to [SailPoint Virtual Appliances](). 4. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 5. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 6. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 7. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default. - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system. - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source. 8. Select **Save**. #### Connector Files > [!NOTE] > > **Screenshot** > > [![Connector Files]()]() 1. Upload the .jar file used for the source. The .jar file in this case, is the ojdbc8.jar file obtained from [Oracle Database 12.2.0.1 JDBC Driver & UCP Downloads](). Any .jar uploaded must be compatible with JDK8. > **Warning** > > Ensure that the file you upload is not vulnerable or malicious. For mTLS authentication using Oracle Wallet mode, you need to upload the following JAR files: oraclepki.jar, osdt\_cert.jar, and osdt\_core.jar. For more information, refer to [Prerequisites for mTLS Authentication](). 2. Select **Save**. ## Connection Settings Provide the information required for SailPoint to connect and authenticate with the Oracle Database. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() > [!NOTE] > > By default, SQL Authentication is selected as **Authentication Type**. > [!NOTE] > > To connect using mTLS authentication, refer to [Connection Settings using mTLS Authentication](<#connection-settings-using-mtls-authentication>). 1. Select **Authentication Type** as SQL Authentication. 2. Enter the **User Name** and **Password** of the service account that has the required permissions and makes the connection to the database. 3. Enter the **Database URL** of your Oracle Database installation and the fully qualified name of the Oracle server. The URL format can be either of the following: ```text jdbc:oracle:thin:@:: jdbc:oracle:thin:@::/SERVICE_NAME ``` 4. In **Driver Class**, enter the detailed database driver that connects to the server. For example: ```text oracle.jdbc.driver.OracleDriver ``` 5. In **Additional Connection Parameters**, specify the additional connection parameters and their values that must be passed in key value pair format. This is to support the network encryption and data integrity feature for the Oracle Database managed target system, which is recommended by the Oracle server as a part of standard security feature. If multiple parameters need to be specified, they should be entered in a new line. For example, you can enter the following: ```text oracle.net.encryption_client=ACCEPTED oracle.net.encryption_types_client=AES256 ``` 6. Select **Save**. ### Connection Settings Using Kerberos Authentication Provide the information required for SailPoint to connect and authenticate with the Oracle Database using Kerberos. The connector supports two credential modes for Kerberos authentication: | Mode | Description | | --- | --- | | **Keytab** | Uses a keytab file and JAAS configuration to authenticate without a password. Recommended for production environments. | | **Password** | Uses a Kerberos principal and password to authenticate. | 1. Select **Authentication Type** as Kerberos Authentication. 2. Select the **Credential Mode** you have configured for Kerberos authentication. > **Keytab** > > 1. In the **Configuration File Path** field, enter the directory path on the VA where the `krb5.config`, `OracleJDBCDriver.config`, and keytab files are located. > > ```text > /home/sailpoint/oracle-kerberos/ > ``` > > > **Note** > > > > Leave this field blank to use the default directory if the files are uploaded using the upload option on the [Base Configuration](<#base-configuration>) page. > 2. Select the **Kerberos Configuration Source**: > > - **Configuration File (krb5.config)** - Uses the `krb5.config` file placed in the Configuration File Path. This is the recommended approach. > - **Realm and KDC** - Enter the Kerberos realm and KDC hostname directly. Use this if you do not want to place a `krb5.config` file on the VA. > 3. If you selected **Realm and KDC**, enter the following: > > - In **Kerberos Realm**, enter the realm name in uppercase. For example, `EXAMPLE.COM`. > - In **KDC Hostname**, enter the fully qualified hostname of the Key Distribution Center. For example, `dc.example.com`. > **Password** > > 1. In the **Kerberos Principal** field, enter the principal in the format `username@REALM`. > > ```text > ora_kerb@EXAMPLE.COM > ``` > 2. In the **Kerberos Password** field, enter the Active Directory password for the Kerberos principal. > 3. In the **Configuration File Path** field, enter the directory path on the VA where the `krb5.config` and `OracleJDBCDriver.config` files are located. > > ```text > /home/sailpoint/oracle-kerberos/ > ``` > > > **Note** > > > > Leave this field blank to use the default directory if the files are uploaded using the upload option on the [Base Configuration](<#base-configuration>) page. > 4. Select the **Kerberos Configuration Source**: > > - **Configuration File (krb5.config)** - Uses the `krb5.config` file placed in the Configuration File Path. This is the recommended approach. > - **Realm and KDC** - Enter the Kerberos realm and KDC hostname directly. > 5. If you selected **Realm and KDC**, enter the following: > > - In **Kerberos Realm**, enter the realm name in uppercase. For example, `EXAMPLE.COM`. > - In **KDC Hostname**, enter the fully qualified hostname of the Key Distribution Center. For example, `dc.example.com`. 3. Enter the **Database URL** of your Oracle Database installation. Use the following format: ```text jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=))(CONNECT_DATA=(SERVICE_NAME=))) ``` - `` - IP address or fully qualified domain name (FQDN) of the Oracle server. - `` - TCP listener port. The default is `1521`. - `` - Oracle service name exactly as registered with the listener. > **Note** > > Ensure the Oracle server hostname is resolvable from the Virtual Appliance. If the hostname is not resolvable via DNS, configure a `hosts.yaml` file on the VA. Refer to [Configuring a hosts.yaml File](). > **Note** > > Unlike mTLS authentication, Kerberos authentication uses the standard TCP protocol (not TCPS). The Kerberos token is exchanged at the application layer via the Oracle JDBC thin driver's built-in GSSAPI support. 4. In **Driver Class**, enter the detailed database driver that connects to the server. For example: ```text oracle.jdbc.driver.OracleDriver ``` 5. In **Additional Connection Parameters**, specify the additional connection parameters and their values that must be passed in key value pair format. If multiple parameters need to be specified, they should be entered in a new line. 6. Select **Save**. ### Connection Settings Using mTLS Authentication Provide the information required for SailPoint to connect and authenticate with the Oracle Database. > [!NOTE] > > **Screenshot** > > [![Connection Settings using mTLS Authentication]()]() 1. Select **Authentication Type** as mTLS Authentication. 2. Select the **Authentication Mode** you have configured for mTLS authentication. > **Oracle Wallet** > > [![Oracle Wallet]()]() > > 1. In the **Oracle Wallet path** field, provide the filesystem path to the wallet directory on the VA. > > ```text > /home/sailpoint/oracle_wallet/ > ``` > 2. In the **Oracle Wallet Password** field, provide the wallet password if `ewallet.p12` file is used. > **Java Keystore (JKS / PKCS12) Mode** > > [![Java Keystore (JKS / PKCS12) Mode]()]() > > 1. In the **Client Keystore Path** field, enter the file path to the client identity file (.p12 or .jks) that contains both the certificate and private key. > > ```text > /home/sailpoint/client/client.p12 > ``` > 2. In the **Client Keystore Password** field, enter the password for the keystore file. > 3. In the **Client Key Password** field, enter the private key password if it is different from the keystore password. Leave this blank if the private key uses the same password as the keystore. > 4. In the **Client Truststore Path** field, enter the file path to the truststore (.jks or .p12) that contains the CA certificates used to validate the server. > > ```text > /home/sailpoint/client/client-truststore.jks > ``` > 5. In the **Client Truststore Password** field, enter the password for the client truststore file. 3. Enter the **Database URL** of your Oracle Database installation and the fully qualified name of the Oracle server. Use the following format: > **Note** > > When using mTLS authentication, the Database URL must use the TCPS protocol and include the Oracle server certificate's Subject DN for server identity verification. ```text jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)(HOST=)(PORT=))(CONNECT_DATA=(SERVICE_NAME=))(SECURITY=(SSL_SERVER_CERT_DN=""))) ``` - `` - IP address or fully qualified domain name (FQDN) of the Oracle server. - `` - TCPS listener port. The default is `2484`. - `` - Oracle service name exactly as registered with the listener. - `` - Subject DN of the Oracle server certificate, for example: `CN=oracle-server.example.com,OU=Oracle,O=YourOrg,C=US`. > **Note** > > Ensure the hostname is resolvable from the Virtual Appliance. Refer to [Configuring a hosts.yaml File](). 4. In **Driver Class**, enter the detailed database driver that connects to the server. For example: ```text oracle.jdbc.driver.OracleDriver ``` 5. In **Additional Connection Parameters**, specify the additional connection parameters and their values that must be passed in key value pair format. This is to support the network encryption and data integrity feature for the Oracle Database managed target system, which is recommended by the Oracle server as a part of standard security feature. If multiple parameters need to be specified, they should be entered in a new line. For example, you can enter the following: ```text oracle.net.ssl_version=1.3 ``` 6. Select **Save**. ## Additional Settings > [!NOTE] > > **Screenshot** > > [![Additional Settings]()]() 1. Select **Use Execute Query** to run the execute method for the selected Oracle Database statements while processing and returning the objects. 2. In the **Chunk To Fetch** field, you can specify the chunk size for all operations. This is a number of rows of result set. 3. Select **Save**. ## Review and Test Perform a test to confirm the connection to SailPoint. 1. Go to **Review and Test**. 2. Confirm that the entries in each field are correct. If you note any mistakes, return to the section and make corrections. 3. Select **Test Connection**. ## SailPoint Application Onboarding SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface. For more information, refer to [Application Onboarding]() in the SailPoint SaaS documentation. # Integrating SailPoint with Oracle Database > [!IMPORTANT] > > This is an advanced connector for accounts. Please open a support ticket for assistance. This is a standard connector for provisioning. The SailPoint Oracle Database integration is capable of end-to-end user administration with provisioning and password management capabilities of Oracle database, helping provide rich governance and control experience to the enterprise. If you have user accounts in Oracle Database that you want to load into SailPoint, you can create a direct connect source for Oracle Database and load that data into your system. To manage that data, [either create an identity profile]() based on the source or verify that the accounts you load are [correlated]() to an existing identity. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The Oracle Database connector supports the following features: > [!NOTE] > > Before you can use any feature marked with an asterisk (\*), SailPoint must activate the feature for your site. - Authentication - Accounts - \*Password Management - \*Provisioning - \*Access Certifications (certification of entitlements connected to accounts) For more information on features, refer to [Source Features](). In account - entitlement management, the Oracle Database connector supports the management of Oracle entitlements as system privileges. - Management of Oracle groups as ROLE - Aggregation and Refresh entitlement - Create, Update, and Delete The Oracle Database source supports: - Permissions directly assigned to accounts and groups as direct permissions during account and entitlement aggregation. - Revocation of the aggregated permissions for an account through certification. The details of the features are: **Accounts** | Features | Users | | --- | --- | | Create | ✔ | | Aggregate | ✔ | | Enable/ Disable | ✔ | | Password Management | ✔ | | Group Entitlements (Read, Request, and Revoke) | ✔ Roles | | Additional Entitlements | SYSTEM\_PRIVILEGES | | Enable Direct Permissions | ✔ | **Group Entitlements** Group Entitlements are the entitlement types for which SailPoint provides the ability to aggregate additional details of these entitlement types from the managed system. These objects have separate schema defining the list of attributes that the aggregation task fetches as additional details when aggregation is run for that Group Entitlement type. The group hierarchy for the Roles attribute is supported. | Features | Users | | --- | --- | | Aggregation | ✔ | | Direct Permissions | ✔ | | Read Group Hierarchy | ✔ | To enable direct permissions and their aggregation for the account or the group schema of your Oracle Database source, perform the following steps. 1. Use [listSources]() API to get the source ID for your source. 2. Use [listSchemas]() API to get the schema ID for the account or group schema for which you want to enable direct permissions. 3. Use [updateSchema]() API and enter the following content in the body. ```json { "op": "replace", "path": "/includePermissions", "value": true } ``` ### Privilege Classification SailPoint Privilege Classification helps organizations systematically categorize and manage the privilege levels of entitlements within their sources. By classifying entitlements as high, medium, or low, administrators can better understand the potential risk and impact associated with specific access rights. This allows automatic assignment of privilege levels based on system recommendations, custom-defined criteria, or a same level across all entitlements. | Privilege Level | Description | | --- | --- | | High | Administrative level access to accounts | | Medium | Administrative level access for a specific role or function | | Low | Only basic access of data | > [!NOTE] > > To manage Privilege Classification, users must have administrative roles such as Org Admin, Source Admin or Source Sub-Admin. For more information, refer to [Managing Privilege Classification](). ### Password Management If Password Management is enabled for your organization, you can change the password for a user of the source. After enabling password management on the source, be aware of the following: - The password policy defined in SailPoint applies to accounts on this source. - If you change the password for an application connected to this source, the change will automatically be made to the source itself. For more information on configuring password management, refer to [Password Management Overview](). ## Supported Managed Systems The SailPoint Oracle connector supports the following versions of the Oracle Server: - Oracle Database 23ai - Oracle Database 21c - Oracle Database 19c - Oracle Database 18c - Oracle Database 12cR2 - Oracle Database 12c > [!NOTE] > > The connector manages users and groups of Oracle 23ai, 21c, 19c, 18c, 12c, and 12cR2 for: > > - Pluggable database (PDB) > - Container database (CDB) at current container level The SailPoint Oracle connector supports managing Oracle Databases hosted on Amazon Web Services Relational Database Service (AWS RDS). For more information on AWS RDS, refer to [Amazon Web Services Relational Database Service (AWS RDS)](<#amazon-web-services-relational-database-service-aws-rds>). > [!NOTE] > > The Oracle Database connector does not support the Oracle Versions 11g and 10g. ### Amazon Web Services Relational Database Service (AWS RDS) AWS RDS Oracle is a managed service provided by Amazon that has certain restrictions on what an administrative account can perform on the Oracle Database instance on AWS RDS. As a result of these restrictions, the SailPoint Oracle connector supports Oracle on AWS RDS with the following limitations: - Application configuration attributes are the same. - By default, the Oracle Database connector aggregates all the roles, system privileges, and profiles as entitlements where profiles are not requestable. Among the aggregated roles/system privileges, the master user does not have all the permissions for provisioning on an AWS RDS instance. - For creation of the service account, the following permissions (in reference to the permissions mentioned in [Required Permissions](<#required-permissions>)) cannot be assigned to the service account by the master user: - `GRANT GRANT ANY ROLE TO ${UserName};` - `GRANT GRANT ANY PRIVILEGE TO ${UserName};` - `GRANT SELECT ON dba_col_privs TO ${UserName};` - `GRANT SELECT ON V_$version TO ${UserName};` - `GRANT SELECT on V_$PWFILE_USERS to ${UserName};` - In order to enable the service account to grant the role (which is allowed on RDS) to a user, the following permission must be given to the service account through the master user: ```text GRANT TO ${UserName} WITH ADMIN OPTION ``` For assigning the service user permissions, use the SQL script located at this location: [https://community.sailpoint.com/docs/DOC-11323]() This script grants all the permissions available with the master user **WITH ADMIN OPTION=YES** to the service user. - In cases where you use custom roles created by the master user or any other user which is equivalent to the **master**, the owner of the role must assign the role to the service user using the WITH ADMIN OPTION. - For the table/system privileges, the revoke option is available with the user who has granted them. ## Prerequisites - Configure at least one virtual appliance cluster and successfully test the connection. For instructions, refer to the [Virtual Appliance Reference Guide](). - Identify or create a service account on the Oracle Database system. - Obtain the custom Oracle jar file ojdbc8.jar from [Oracle Database 12.2.0.1 JDBC Driver & UCP Downloads](). - For mTLS authentication, complete the requirements in [Prerequisites for mTLS Authentication](<#prerequisites-for-mtls-authentication>). ### Prerequisites for mTLS Authentication Your Oracle DBA must complete the following on the Oracle Database server before you configure the connector: - Configure the Oracle listener to accept TCPS connections, typically on port `2484`. - Enable client certificate authentication (`SSL_CLIENT_AUTHENTICATION = TRUE` in `sqlnet.ora`). - Create a minimum permission user as below: ```sql CREATE USER "username" IDENTIFIED EXTERNALLY; ``` Example: ```sql CREATE USER MTLSUSER IDENTIFIED EXTERNALLY AS 'CN=jmtlsclient,OU=SailPoint,O=Lab,C=US'; ``` - Grant the required permissions to the database user. Refer to [Required Permissions](<#required-permissions>) for more information. > [!NOTE] > > Oracle reads certificate Subject DNs in X.500 order - least-specific attribute first (for example, `C=` before `CN=`). The external name on the database user must match this format exactly. To confirm the exact DN format, use the `orapki cert display` utility on the Oracle server and inspect the **Subject** field of the client certificate. > [!NOTE] > > To use Oracle Wallet mode, upload *OraclePKI* jars to the source config. *OraclePKI* jar version must be compatible with the ojdbc driver jar version. > > - `oraclepki.jar` > - `osdt_cert.jar` > - `osdt_core.jar` > [!NOTE] > > **Server Side Files** > > **Oracle Wallet Mode**: > > - `cwallet.sso` - Auto-login server wallet - opened by the Oracle listener at startup; no password required > - `ewallet.p12` - Password-protected server wallet - contains the server certificate, private key, and the trusted client certificate > > **Java Keystore Mode**: > > - `cwallet.sso` / `ewallet.p12` - Contains the server certificate and private key and client certificate; used by the Oracle listener > - `server.crt` - Oracle server's public certificate - exported from the server wallet > [!NOTE] > > **Oracle Wallet Configuration on VA** > > The following files must be placed on the VA before configuring the source. These are typically generated and maintained by the Oracle/customer PKI team. > > #### Oracle Wallet Directory > > The Oracle Wallet directory contains the client certificate, private key, and the Oracle server's CA certificate for server identity verification. The wallet directory contains the following files: > > | File | Description | > | --- | --- | > | `cwallet.sso` | Auto-login wallet - no password required at runtime | > | `ewallet.p12` | Password-protected wallet - password required at runtime | > > On the VA, place `cwallet.sso` or `ewallet.p12` in a directory at a secure path, for example: > > ```text > /home/sailpoint/certificate/ > ``` > > > **Note** > > > > Auto-login wallets (`cwallet.sso`) do not require a password at runtime. Password-protected wallets (`ewallet.p12`) require the wallet password to be entered in the source configuration. > [!NOTE] > > **Java Keystore Configuration on VA** > > The following files must be placed on the VA before configuring the source. These are typically generated and maintained by the Oracle/customer PKI team. > > #### Java Keystore Directory > > The Java Keystore directory contains the client's private key and certificate used to authenticate to Oracle, and the Oracle server's CA certificate used to verify the server's identity during the TLS handshake. The directory contains the following files: > > | File | Description | > | --- | --- | > | `client.p12` or `client.jks` | Client keystore - contains the client's private key and certificate | > | `truststore.p12` or `truststore.jks` | Client truststore - contains the Oracle server's CA certificate | > > On the VA, place `client.p12`/`client.jks` and `truststore.p12`/`truststore.jks` files in a directory at a secure path, for example: > > ```text > /home/sailpoint/certificate/keystore/ > ``` > > > **Note** > > > > Both the client keystore and truststore must be accessible to the VA at runtime. Ensure the directory and files have the correct permissions before configuring the source. #### Responsibility for File Preparation | File | Responsible Party | | --- | --- | | Oracle server certificate (imported into the client truststore) | Oracle/customer PKI team | | Client certificate and keystore | SailPoint implementer or Oracle/customer PKI team, depending on the deployment model | ### Prerequisites for Kerberos Authentication Your Active Directory administrator and Oracle DBA must complete the following before you configure the connector: **Active Directory Configuration:** - Create a **client principal** (AD user account) for the connector to authenticate as (for example, `ora_kerb@EXAMPLE.COM`). Enable AES256 encryption on this account (`msDS-SupportedEncryptionTypes` must include AES256). - Create a **service account** (AD user account) with an SPN registered for the Oracle service in the format `oracle/` (for example, `oracle/oracle-server.example.com`). - Generate a **client keytab** for the client principal using `ktpass` with AES256-SHA1 encryption. - Generate a **service keytab** for the Oracle SPN using `ktpass` and place it on the Oracle server. > [!NOTE] > > After running `ktpass`, the AD account's password is reset. Set `PasswordNeverExpires` and `CannotChangePassword` on both accounts to prevent key version number (kvno) mismatches. **Oracle Database Server Configuration:** - Configure Kerberos authentication in `sqlnet.ora` with the following parameters: - `SQLNET.AUTHENTICATION_SERVICES = (KERBEROS5)` - `SQLNET.AUTHENTICATION_KERBEROS5_SERVICE` - set to the Kerberos service name (for example, `oracle`) - `SQLNET.KERBEROS5_CONF` - path to the `krb5.ini` file on the Oracle server - `SQLNET.KERBEROS5_KEYTAB` - path to the service keytab on the Oracle server - `SQLNET.KERBEROS5_CONF_MIT = TRUE` - `SQLNET.KERBEROS5_CLOCKSKEW` - clock skew tolerance in seconds (for example, `300`) - Create a `krb5.ini` (or `krb5.config`) on the Oracle server with the realm, KDC address, and encryption type information matching the Active Directory configuration. - Restart the Oracle listener and database services after making these changes. - Create an Oracle database user identified externally. The username must match the Kerberos client principal exactly (case-sensitive, including the realm): ```sql CREATE USER "ORA_KERB@EXAMPLE.COM" IDENTIFIED EXTERNALLY; ``` - Grant the database user `CREATE SESSION` and the required permissions. Refer to [Required Permissions](<#required-permissions>) for more information. > [!NOTE] > > Ensure `os_authent_prefix` is set to an empty string (`''`) on the Oracle instance. If it is set to a non-empty value (for example, `OPS$`), Oracle prepends it to the Kerberos principal before matching, causing authentication failures. > [!NOTE] > > Validate the Kerberos setup locally on the Oracle server before configuring the connector. Use Oracle's `okinit` utility to obtain a TGT and `sqlplus /@` to confirm Kerberos login works end-to-end. #### Kerberos Configuration Files on the VA The following files must be placed on the VA before configuring the source. Place all files in a single directory, for example `/home/sailpoint/oracle-kerberos/`. | File | Description | Required For | | --- | --- | --- | | `krb5.config` | Kerberos configuration - defines the realm, KDC address, and encryption types. Must match the Active Directory domain configuration. | Keytab and Password modes (when using Configuration File) | | `OracleJDBCDriver.config` | JAAS login module configuration - tells the Java Kerberos login module how to authenticate (keytab path, principal, and related settings). | Keytab and Password modes | | `.keytab` | Client keytab file - contains the encrypted key for the client principal. Generated by the AD administrator using `ktpass`. | Keytab mode only | > [!NOTE] > > The `keyTab` path in `OracleJDBCDriver.config` must point to the exact location of the keytab file on the VA. A path mismatch causes authentication failures. > [!NOTE] > > Use the IP address of the KDC in the `krb5.config` on the VA if the KDC hostname is not resolvable from the VA network. If FQDN is used, configure a `hosts.yaml` on the VA. Refer to [Configuring a hosts.yaml File](). ## Required Permissions The service account (user) on the target systems must have permissions for the operations it carries out. | Operation | Required Permissions | | --- | --- | | Load Accounts | Read Permissions | | Provision Accounts | Write Properties
Write User Objects
Create User Objects | | Password Management | Change Password
Reset Password | | Enable and Disable Accounts | Read Account
Write Account | | Unlock Accounts | Read Lockstatus
Write Lockstatus | **Additional Permissions** Update the service account for the Oracle Database source with the following permissions: ```text GRANT SELECT ON DBA_TABLESPACES TO ${UserName}; ``` ```text GRANT SELECT ON DBA_PROFILES TO ${UserName}; ``` The Oracle administrator must have all the permissions mentioned below for performing the provisioning operations. Sign in with administrator credentials and execute the following command to create a new user: ```sql CREATE USER ${UserName} IDENTIFIED BY ${Password}; ``` The following table lists the required permissions for the specific operations mentioned below in this section: | Operation | Required Permissions | | --- | --- | | Test Connection | [Test Connection](<#test-connection>) | | Account Aggregation | [Test Connection](<#test-connection>) and [Account Aggregation](<#account-aggregation>) | | Group Aggregation | [Test Connection](<#test-connection>) and [Group Aggregation](<#group-aggregation>) | | CREATE Account | [Test Connection](<#test-connection>), [Account Aggregation](<#account-aggregation>) and [Create Account](<#create-account>) | | UPDATE / MODIFY Account | [Test Connection](<#test-connection>), [Account Aggregation](<#account-aggregation>) and [UPDATE/MODIFY Account](<#update-account>) | ### Test Connection **SELECT Permission** ```text GRANT create session TO ${UserName}; ``` For the CDB service account, the above permission must be in the following format: ```text GRANT CREATE SESSION to container=CURRENT; ``` ### Account Aggregation **SELECT Permission** ```text GRANT SELECT ON dba_users TO ${UserName}; (By this command discovering schema is possible) GRANT SELECT ON dba_sys_privs TO ${UserName}; GRANT SELECT ON dba_role_privs TO ${UserName}; ``` > [!NOTE] > > To view Sysdba privileges: `SELECT * FROM V$PWFILE_USERS` For the CDB service account, the above permissions must be in the following format: ```text GRANT SELECT ON dba_users TO container=CURRENT; ``` ### Group Aggregation **SELECT Permission** - `GRANT SELECT ON dba_roles TO ${UserName};` (By this command discovering schema is possible) - `GRANT SELECT ON dba_tab_privs TO ${UserName};` - `GRANT SELECT ON dba_col_privs TO ${UserName};` - `GRANT SELECT ON dba_sys_privs TO ${UserName};` - `GRANT SELECT ON system_privilege_map TO ${UserName};` - `GRANT SELECT ON V_$version TO ${UserName};` - `GRANT SELECT on V_$PWFILE_USERS to ${UserName};` - `GRANT SELECT ON dba_role_privs TO ${UserName};` > [!NOTE] > > To view Sysdba privileges: `SELECT * FROM V$PWFILE_USERS` For the CDB service account, the above permissions must be in the following format: ```text GRANT SELECT ON dba_roles TO container=CURRENT; ``` ### Create Account | Account | Role | Profile | | --- | --- | --- | | `GRANT CONNECT TO ${UserName};` | `GRANT CREATE ROLE TO ${UserName};` | `GRANT CREATE PROFILE TO ${UserName};` | | `GRANT CREATE USER TO ${UserName};` | `GRANT CREATE ROLE TO ${UserName};` | `GRANT CREATE PROFILE TO ${UserName};` | | `GRANT GRANT ANY ROLE TO ${UserName};` | `GRANT CREATE ROLE TO ${UserName};` | `GRANT CREATE PROFILE TO ${UserName};` | | `GRANT GRANT ANY PRIVILEGE TO ${UserName};` | `GRANT CREATE ROLE TO ${UserName};` | `GRANT CREATE PROFILE TO ${UserName};` | | `GRANT SELECT ON DBA_TABLESPACES TO ${UserName};` | `GRANT CREATE ROLE TO ${UserName};` | `GRANT CREATE PROFILE TO ${UserName};` | | `GRANT SELECT ON DBA_PROFILES TO ${UserName};` | `GRANT CREATE ROLE TO ${UserName};` | `GRANT CREATE PROFILE TO ${UserName};` | For the CDB service account, the above permissions must be in the following format: **Connect account** ```text GRANT CONNECT TO container=CURRENT; ``` **All other permissions** ```text GRANT CREATE ROLE TO container=ALL; ``` ### Update Account | Account | Role | Profile | | --- | --- | --- | | `GRANT ALTER USER TO ${UserName};` | `GRANT ALTER ANY ROLE TO ${UserName};` | `GRANT ALTER PROFILE TO ${UserName};` | For the CDB service account, the above permissions must be in the following format: ```text GRANT ALTER USER TO container=ALL; ``` # Machine Account Attributes Machine account attributes are used in provisioning configurations for machine accounts. After you have [created the required machine account subtypes](), you can use the machine account attributes to provision machine accounts in your SailPoint tenant. Refer to [Machine Identity Security Overview]() for more information. ## Machine Account Provisioning Attributes | Create Account Attribute | Description | | --- | --- | | USERNAME | Must be replaced with a unique Oracle user identifier for machine account creation. | | password | No default transform; provide only if required by downstream policy/process. | | DEFAULT\_TABLESPACE | Optional. | | TEMPORARY\_TABLESPACE | Optional. | | PROFILE | Optional. | # Provisioning The Oracle Database connector supports provisioning, allowing you to create and manage accounts and entitlements in Oracle Database directly from SailPoint. **Prerequisite:** Your system is configured for provisioning. When SailPoint provisions new accounts to the source, it uses the attributes on the **Create Account** page as instructions or a template for what to include in the account. This page is also referred to as the *provisioning policy*. When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment. For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account. > [!IMPORTANT] > > This section describes the default **Create Account** configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail. ## Default Create Account Attributes #### Attribute Details When SailPoint provisions new accounts to an Oracle Database direct connect source, it uses the attributes on the Create Profile page as instructions or a template for what to include in the account. This page is also referred to as the provisioning policy. > [!IMPORTANT] > > This page describes the configuration of the default Create Profile. However, SailPoint recommends that you [work with Services]() to define a Create Profile specific to your company's needs. > [!NOTE] > > Parameters marked with an asterisk (\*) are mandatory. | Account Attribute | Generator | Description | | --- | --- | --- | | USERNAME\* | Create Unique Account ID | This generator uses the value in the Pattern Used field to generate a unique DN for the new account.

**Caution:** You must change the OU in the Pattern Used field in the `distinguishedName` attribute. | | password | Create Password | This generator creates an initial password for the new account that matches the password policy assigned to the associated Oracle Database source. | | DEFAULT\_TABLESPACE | Static | This is the default value for the tablespace for objects that the user creates. | | TEMPORARY\_TABLESPACE | Static | This is the temporary value for the tablespace for objects that the user creates. | | PROFILE | Static | Profile is a set of limits on database resources and password access to the database. | > [!NOTE] > > For the Oracle Database connector, the default SYSTEM\_PRIVILEGE "CREATE SESSION (ADMIN\_OPTION ='NO')" is granted during account creation. # Schema Reference The application schema is used to configure the objects returned from a connector. > [!NOTE] > > - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas]() for more information. > - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified. The Oracle Database connector uses the following default correlation and object configurations. ## Default Account Schema Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location. The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas]() for more information. ### Default Account ID SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*. > [!CAUTION] > > Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts. > > To resolve issues caused by changing account IDs, reconfigure them to their default values. The following table lists the default account IDs for this connector: | Account ID | Schema Object Type | | --- | --- | | USERNAME | Account | | Role | Group | ### Default Account Attributes The Oracle Database connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified. | Attribute Name | Description | | --- | --- | | USERNAME | The user name.
This is an Account ID which must not be changed. | | USER\_ID | The user ID. | | ACCOUNT\_STATUS | The account status. | | DEFAULT\_TABLESPACE | The default tablespace. | | ROLES | The roles assigned to the user. | | PROFILES | The profiles assigned to the user. | | TEMPORARY\_TABLESPACE | The temporary tablespace. | | SYSTEM\_PRIVILEGES | The system privileges assigned to the user.

**Note:** SYSDBA and SYSOPER permissions are visible under SYSTEM\_PRIVILEGES. | | AUTHENTICATION\_TYPE | The authentication type values:
\- NONE (When role is updated)
\- EXTERNAL
\- GLOBAL
\- PASSWORD | ## Include Permissions in Account Schema When permissions are aggregated (For example, when `includePermissions="true"` is set to true in the account schema definition and the `privilege` attribute is included in the account schema), the permissions are aggregated under the `directPermissions` attribute, not the `privilege` attribute itself. This data is not visible in the UI but is included in the link or identity XML/JSON. ## Default Entitlement Attributes Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements]() for more information. > [!CAUTION] > > Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations. ### Default Group Attributes The Oracle Database connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups. | Attribute Name | Description | | --- | --- | | ROLE | The role name.
This is an Account ID which must not be changed. | | AUTHENTICATION\_TYPE | The authentication type. The possible values are:
\- NONE (When role is updated)
\- EXTERNAL
\- GLOBAL
\- PASSWORD | | SYSTEM\_PRIVILEGES | The system privileges assigned to the role. | | ROLES | The roles assigned to the role. | | PASSWORD\_REQUIRED | Specifies whether a password is required or not. | # TLS Support for Oracle Database The Oracle Database connector supports TLS communication. While SailPoint internally supports TLS version 1.2, it can communicate with the Oracle Database source using any version of TLS the source supports. To use a TLS-based connection for the Oracle Database connector, ensure that you have completed the following. - Save the Oracle Server certificates on the virtual appliance at location `/home/sailpoint/certificates` and restart the CCG. - Provide the `PROTOCOL`, `HOST`, `PORT`, and `SERVICE_NAME` parameters in Oracle database application URL in the following format: ```text jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=)(PORT=))(CONNECT_DATA=(SERVER = DEDICATED)(SERVICE_NAME = ))) ``` For example: ```text jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=WIN-0PR71D80V83)(PORT=2500))(CONNECT_DATA=(SERVER = DEDICATED)(SERVICE_NAME = orcx))) ``` # Enable Connector Logging This topic provides the steps needed to enable logging on SailPoint using REST APIs. > [!NOTE] > > This topic only applies to VA-based integrations. > [!NOTE] > > The examples provided might not match your configuration. Use the logging levels and logging classes reference at the bottom of the topic to configure your API responses to match your connector. This process is broken up into four steps: 1. Identify the Virtual Appliance (VA) cluster on which you want to enable logging. 2. Get the logging configuration for the existing VA cluster. 3. Update the VA cluster to enable logging levels. 4. Observe logging changes to the logging levels. ### Identify the Virtual Appliance Cluster Select the VA on which you need to enable logging using REST API. If you already know the VA application's `id`, proceed to [Get the Logging Configuration](<#get-the-logging-configuration>). 1. Make the following call to the REST API to return a list of available VA clusters: GET /v3/managed-clusters The REST API returns a response that looks similar to the following: ```json [ { "id": "2c9180866166b5b0016167c32ef31a66", "name": "Development Cluster", "description": "Development Cluster", "clientType": "CCG", "ccgVersion": "373_535_70.2.0", "pinnedConfig": true, "logConfiguration": null }, { "id": "2c9180846a93ce60016ab29f039944de", "name": "Cloud Cluster", "description": "Cloud Cluster", "clientType": "CCG", "ccgVersion": "373_535_70.2.0", "pinnedConfig": true, "logConfiguration": { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } } ] ``` > **Note** > > The previous example code shows two VA clusters. One VA cluster has a log configuration and the other does not (refer to the `logConfiguration` value in each returned VA cluster). This is because one of the clusters already has logging enabled. This is just an example configuration, and your environment may not have logging enabled on a cluster. 2. Identify the VA cluster that you want to enable logging on by its name or description and record its `id` attribute. ### Get the Logging Configuration Get your selected VA's cluster logging configuration and identify the values you need to update. 1. Make the following call to the REST API to return the VA cluster's logging configuration. Replace `{id}` with the VA cluster's `id` attribute value recorded earlier. GET /v3/managed-clusters/{id}/log-config - If the VA doesn't have a logging configuration currently set, it returns `204 No Content` as a response. - If the VA has an existing logging configuration, it returns something similar to the following: ```json { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` You'll need to configure the following information in the response: - `durationMinutes` is the number of minutes logging should remain enabled. - `rootLevel` is the default level for all logs. For more information, refer to [Logging Levels](<#logging-levels>). - `logLevels` is a map object with logging classes as keys and logging levels as values. - For keys, refer to [Logging Classes](<#logging-classes>) for commonly used logging classes. - For a list of available values, refer to [Logging Levels](<#logging-levels>). ### Update Logging Configuration Update the VA cluster configuration returned by the REST API to update the logging settings as needed. 1. Make the following call to the REST API to update the VA cluster's logging configuration. Replace `{id}` with the VA cluster's `id` attribute value recorded earlier. PUT /v3/managed-clusters/{id}/log-config 2. Submit your configuration changes to the REST API in a JSON body. - If the VA cluster did not already have a logging configuration and you received a `204 No Content` response, you can create a new one. - If the VA returned a configuration, you can edit it to include the changes. The JSON body should be as follows: ```json { "durationMinutes": 60, "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` Consider the following as you edit the JSON: - `durationMinutes` is the number of minutes logging should remain enabled. - `rootLevel` is the default level for all logs. For more information, refer to [Logging Levels](<#logging-levels>). - `logLevels` is a map object with logging classes as keys and logging levels as values. - For keys, refer to [Logging Classes](<#logging-classes>) for commonly used logging classes. - For a list of available values, refer to [Logging Levels](<#logging-levels>). If the update was successful, the REST API should return a response similar to the following: ```json { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` ### Observe Logging Changes Approximately five minutes after you update the configuration, the VA cluster starts generating log files you can review. You can view the log files in **ccg.log**. ### References The tables in this reference section list information that can be helpful when creating the JSON body you'll use to configure the VA cluster's configuration file. #### Logging Levels | Logging Level | Description | | --- | --- | | ERROR | Designates error events that might still allow the connector to continue. | | WARN | Designates potentially harmful situations. | | INFO | Designates information messages that highlight process at a coarse-grain level. | | DEBUG | Very verbose. Fine grain logging levels used for development and debugging. | | TRACE | Most verbose. Finer grain logging levels than debugging. | #### Logging Classes | Connector | Logging Class | | --- | --- | | Active Directory | sailpoint.connector.ADLDAPConnector sailpoint.connector.LDAPConnector | | AIX | openconnector.connector.unix.AIXConnector openconnector.connector.unix.UnixConnector | | Amazon Web Services | logger.aws.name=openconnector.connector.aws logger.aws.level=trace logger.aws.additivity = false logger.aws.appenderRef.rolling.ref = STDOUT | | Atlassian Suite Cloud | sailpoint.connector.OpenConnectorAdapter openconnector.connector.atlassian.AtlassianConnector | | Atlassian Data Center | sailpoint.connector.OpenConnectorAdapter openconnector.connector.atlassian.AtlassianDataCenterConnector | | Microsoft Entra ID | sailpoint.connector.AzureADConnector | | Box | openconnector.connector.BoxNetConnector sailpoint.connector.OpenConnectorAdapter | | Cerner | openconnector.connector.CernerConnector sailpoint.connector.OpenConnectorAdapter | | Delimited File | logger.DelimitedFileConnector.name = sailpoint.connector.DelimitedFileConnector logger.DelimitedFileConnector.level = debug logger.DelimitedFileConnector.additivity = false logger.DelimitedFileConnector.appenderRef.rolling.ref = STDOUT | | Dropbox | openconnector.connector.DropBoxConnector sailpoint.connector.OpenConnectorAdapter | | Epic | openconnector.connector.EPICConnector sailpoint.connector.OpenConnectorAdapter | | GE Centricity | openconnector.connector.GECentricity sailpoint.connector.OpenConnectorAdapter | | Google Apps / G Suite | openconnector.connector.GoogleAppsDirect sailpoint.connector.OpenConnectorAdapter | | IBM i | openconnector.connector.IBMiConnector | | Lotus Domino | sailpoint.connector.LotusDomino | | JDBC | sailpoint.connector.JDBCConnector | | Sun One LDAP | sailpoint.connector.LDAPConnector | | Linux | openconnector.connector.unix.LinuxConnector sailpoint.connector.OpenConnectorAdapter sailpoint.connector.UnixConnector | | Microsoft Office365 | sailpoint.connector.Office365Connector | | Microsoft SQL Server | sailpoint.connector.mssql.serviceimpl.MSSQLServerConnectorV2 | | Okta | logger.openconnector.name = openconnector.connector.okta.OktaConnector logger.openconnector.level = debug logger.openconnector.additivity = false logger.openconnector.appenderRef.rolling.ref = STDOUT | | Oracle Database | sailpoint.connector.OracleDBConnector sailpoint.connector.JDBCConnector | | Oracle E-Business | sailpoint.connector.OracleEBSConnector sailpoint.connector.JDBCConnector | | Oracle Fusion HCM | openconnector.connector.oraclefusionhcm.OracleFusionHCMConnector sailpoint.connector.OpenConnectorAdapter | | Oracle HCM Cloud | sailpoint.connector.oraclehcmcloud.OracleHCMCloudConnector | | Oracle HRMS | sailpoint.connector.OracleAppsHRMSConnector sailpoint.connector.JDBCConnector | | Oracle Netsuite | openconnector.connector.netsuite.NetsuiteConnector | | PeopleSoft ERP | openconnector.connector.PeopleSoftConnector sailpoint.connector.OpenConnectorAdapter | | PeopleSoft HRMS | sailpoint.connector.PeopleSoftHRMSConnector | | RemedyForce | sailpoint.connector.ForceConnector | | RSA Authentication Manager | openconnector.connector.RSAConnector openconnector.connector.rsa.RSAHTTPClient sailpoint.connector.OpenConnectorAdapter | | Salesforce | sailpoint.connector.ForceConnector | | SAP Concur | openconnector.connector.sapconcur.SAPConcurConnector | | SAP - Direct | sailpoint.connector.SAPConnector sailpoint.connector.SAPInternalConnector | | SAP GRC | logger.SAPGRCConnector.name = sailpoint.connector.sapgrc logger.SAPGRCConnector.level = debug logger.SAPGRCConnector.additivity = false logger.SAPGRCConnector.appenderRef.rolling.ref = STDOUT | | SAP HR/HCM | sailpoint.connector.SAPHRInternalConnector | | SCIM 1.1 | openconnector.connector.SCIMConnector sailpoint.connector.OpenConnectorAdapter | | SCIM 2.0 | openconnector.connector.scim2.SCIM2Connector sailpoint.connector.OpenConnectorAdapter | | ServiceNow | openconnector.connector.servicenow.ServiceNowConnector openconnector.connector.servicenow.ServiceNowRestClient sailpoint.connector.OpenConnectorAdapter | | ServiceNow Service Desk Integration | openconnector.connector.servicedesk.ServiceNowServiceDeskConnector sailpoint.connector.OpenConnectorAdapter | | Siebel | openconnector.connector.SiebelConnector sailpoint.connector.OpenConnectorAdapter | | Snowflake | openconnector.connector.snowflake.SnowflakeConnector sailpoint.connector.OpenConnectorAdapter | | Solaris | openconnector.connector.unix.SolarisConnector openconnector.connector.unix.UnixConnector sailpoint.connector.OpenConnectorAdapter | | SuccessFactors | sailpoint.connector.SuccessFactorsConnector | | Sybase | sailpoint.connector.SybaseDirectConnector sailpoint.connector.JDBCConnector | | Webex | openconnector.connector.Webex sailpoint.connector.OpenConnectorAdapter | | Workday | openconnector.connector.WorkDay sailpoint.connector.OpenConnectorAdapter | | Workday Accounts | openconnector.connector.workdayaccounts openconnector.connector.workdayaccounts.WorkdayAccountsConnector sailpoint.connector.OpenConnectorAdapter | | Web Services | sailpoint.connector.WebServices | | XML | openconnector.connector.XMLConnector sailpoint.connector.OpenConnectorAdapter | | Yammer | openconnector.connector.YammerConnector sailpoint.connector.OpenConnectorAdapter | | Zoom | openconnector.connector.zoom.ZoomConnector sailpoint.connector.OpenConnectorAdapter | # 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: - [SailPoint Identity Services Documentation]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() ## Create account with 'PASSWORD\_EXP' fails with error **Issue**: When a customer adds `PASSWORD_EXP` to the Account Schema and Create Account policy and triggers a create account operation, the account is created in Oracle DB successfully and the user account status is marked as `EXPIRED`. However, the provisioning request shows the following error message: ```text Error: Please contact your administrator Provisioning sailpoint.connector.ConnectorException: [ ConnectorException ] [ Error details ] The server encountered an unexpected error while contacting target system during get object operation. Please check the logs. The column [PASSWORD_EXP] does not exist ``` **Resolution**: Do not add `PASSWORD_EXP` to the account schema. Add it only to the create policy and execute the provisioning use case. ## Oracle accounts are missing the "CREATE SESSION (ADMIN\_OPTION ='NO')" system privilege Oracle is not adding the "CREATE SESSION (ADMIN\_OPTION ='NO')" automatically while creating accounts. **Resolution**: The Oracle connector does not automatically add "CREATE SESSION (ADMIN\_OPTION ='NO')" while creating an account using the role, it is only applicable while creating an account using the SYSTEM privilege. ## Provisioning SYSDBA and SYSOPER Fails with Insufficient Privileges ```text User entitlements not modified sailpoint.connector.ConnectorException: ORA-01031: insufficient privileges ``` **Resolution**: The user must connect with the user as `" as sysdba"` and the `` must have SYSDBA privileges. ## Access Requests Fail with Role or System Privilege Errors This error message displays when the service user does not have the required permissions available: ```text [ConnectorException] [Error details] NEW The server encountered an unexpected error while contacting target system. Please check the logs. User entitlements not modifiedsailpoint.connector.ConnectorException: ORA-01924: role 'AUDIT_VIEWER' not granted or does not exist [ConnectorException] [Error details] NEW The server encountered an unexpected error while contacting target system. Please check the logs. User entitlements not modifiedsailpoint.connector.ConnectorException: ORA-00604: error occurred at recursive SQL level 1 ORA-20997: "ALTER SYSTEM" grants not allowed ORA-06512: at "RDSADMIN.RDSADMIN", line 79 ORA-06512: at line 2 ``` **Resolution**: Ensure that the roles/system privileges being granted are available for the service user by using the following: `WITH ADMIN OPTION=YES`. ## Provisioning Fails When the USERNAME Column Is Missing ```text The identity attribute USERNAME does not exist in table ``` **Resolution**: The connector performs a Get Object of the provisioned accounts and checks for the `USERNAME` column in the `DBA_USERS` table. Ensure that `USERNAME` is present in the `DBA_USERS` table. ## Testing the Connection Fails with ORA-01882 The following error can occur when you test the connection if you are connecting this source to an 11.2 Oracle database with an Oracle 11.2 ojdbc drive: ```text ORA-01882: timezone region not found ``` **Resolution**: Check the version of the DST file that exists in the database using the following command: `SELECT * FROM v$timezone_file;` If the version number is lower than 18, upgrade the DST file to version 18 or the latest version. # Timeout Errors and Settings Timeout errors might occur when SailPoint is waiting for a response from the Virtual Appliance (VA). These errors are applicable to all connectors and tend to occur during the setup of sources or when sources are down. This document is designed to give specific information that can be used to resolve these errors. Each timeout attribute has a default time value that is listed in seconds or minutes. Increasing the time value may resolve the error as it will allow for longer communication time between the two systems, thus avoiding the timeout error. > [!IMPORTANT] > > Add the necessary attributes or values before performing the "replace" operation, as missing attributes will cause the operation to fail. To increase the communication time, increase the value of the appropriate timeout attribute. Then submit the change to the VA using the SailPoint REST API. > [!NOTE] > > For more information on SailPoint's REST APIs, refer to [Best Practices: REST API Authentication]() and [REST API - Update Source (Partial)]() in the SailPoint Developer Community. ### aggregateTimeout **Description:** This parameter is set for the aggregation timeout, measured in seconds. **Resolution:** Increase the `aggregateTimeout` value gradually to optimize aggregation. Start with 180, then increase to 600, 900, and finally 1800. The maximum value is 3600 seconds. For example: If your current time value is 180 seconds, update the `aggregateTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/aggregateTimeout", "value": 600 } ] ``` ### healthCheckTimeout **Description:** This parameter is set for the test connection and health check timeout. **Resolution:** The default value is 30 seconds. If the timeout error continues, increase the value in 15 second increments and try again. For example: If your current time value is 30 seconds, update the `healthCheckTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/healthCheckTimeout", "value": 45 } ] ``` ### provisioningTimeout **Description:** This parameter is set for provisioning timeout. **Resolution:** Increase the `provisioningTimeout` value gradually to optimize provisioning. Start with 180, then increase to 360, and finally 600. The maximum value is 600 seconds. For example: If your current time value is 180 seconds, update the `provisioningTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/provisioningTimeout", "value": 360 } ] ``` ### timeout **Description:** This parameter is set for pass-through authentication timeout. **Resolution:** The default value is 15 seconds. If the timeout error continues, increase this value in 15 second increments and try again. For example: If your current time value is 15 seconds, update the `timeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/timeout", "value": 30 } ] ``` ### apiTimeout **Description:** This parameter is set for API time tracking; customers can check it using an external tool. **Resolution:** The default value is 60 seconds. If the error continues, increase the value by 15 second increments and try again. For example: If your current time value is 60 seconds, update the `apiTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/apiTimeout", "value": "75" } ] ``` ### timeoutInSeconds **Description:** This parameter helps prevent the VA from waiting indefinitely for an API response, ensuring efficient handling of API requests. For example: If your current time value is 30 seconds, update the `timeoutInSeconds` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/timeoutInSeconds", "value": "15" } ] ```