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 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. |
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.