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 SAP GRC connector uses the following default correlation and object configurations.
Important
The parameters and their respective descriptions of the parameters are mentioned in the following format:
Parameter Name: Description of the parameter
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 |
|---|---|
| User ID (only valid under Access Management Integration Mode) | Account |
| Role UUID | Group |
| FFUserID | FireFighterID |
Default Account Attributes
The SAP GRC connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.
The following lists the account attributes:
| Attribute Name | Description |
|---|---|
| First Name | First name of the user. |
| Last Name | Last name of the user. |
| User ID | ID of the user. This is an Account ID which must not be changed. Only valid under Access Management Integration Mode. |
| Email of the user. | |
| Phone | Telephone number of the user. |
| Department | Department of the user. |
| FireFighterID | The FireFighterID assigned to the user. |
| Manager ID | Manager Id of the user. |
| User Group | User group assigned to a user. |
| User Type | Type of the user. For more information on the abbreviations used for the type of user aggregated, refer to Status of User Type. |
| Valid From | System ID with from validity of the user in a format as SystemID/Date. The date format is yyyymmdd. |
| Valid To | System ID with upto validity of the user in a format as SystemID/Date. The date format is yyyymmdd. |
| Status | User Status (per connector). |
| System | System ID of the connector with highest sequence (priority) maintained in the data source configuration from SPRO. |
| Roles | Roles assigned to a user. |
Status of User Type
The following table lists details about the abbreviations used to represent the type of user aggregated:
| User Type | Description |
|---|---|
| A | Dialog |
| B | System |
| C | Communication Data |
| L | Reference (Logon not possible) |
| S | Service |
Note
"Account Number" (ACCNT) and "Cost Center" (KOSTL) are supported only for provisioning.
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 SAP GRC connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups.
Object Type: Group
| Attribute Name | Description |
|---|---|
| Role UUID | Role universally unique identifier. This is an Account ID which must not be changed. |
| Role Name | Name of the role. |
| Role Desc | Role description. |
| System | System to which role belongs. |
| Role Type | Type of the role. |
| Role Type Desc | Role type description. |
| Landscape | Role landscape. |
| Role Owner | Owner of the role. |
| Business Process | Business Process to which role belongs. |
| Sub Process | Sub Process to which role belongs. |
| Role Status | Role Status. |
| Associated Child Roles | Roles associated with Composite or Business role. |
Object Type: FireFighterID
| Attribute Name | Description |
|---|---|
| FFUserID | The Fire Fighter ID. (Connector + delimiter + FFUserID) |
| Connector | The connector name of the ID. |
| FFOwner | The owner who approves access and monitors usage. |
| FFController | The controller who reviews logs and adds comments. |
| DefaultValidityDays | The default validity dates for usage of ID. |
| Roles | The roles assigned to Firefighter ID. |
Considerations for Schema Attributes
- The connector aggregates the value for the following account attributes based on the connector that is maintained in the highest sequence in the User Detail Data Source:
- First Name
- Last Name
- User ID
- Phone
- Department
- Manager ID
- User Type
- The connector aggregates the Role name in the format
System Name/Role Name- for example,HANADB/CONTENT_ADMIN. For the GRC business role, only the Role Name is displayed. - Update account is supported during the Create Account operation for all the account attributes except for the Status attribute.
- If values are changed by the GRC administrator after a request is created, that request is not completed.
- Only the Add and Remove operations are supported.
- The Request ID is sent to GRC for every provisioning operation and is not available in the UI during certification.
- Line item approval and rejection (only) is supported for the Role attribute from the GRC side.
- An Identity Status as Enabled or Disabled is mapped to the Locked/Unlocked status of the user in the system. If there are multiple systems, it is based on the order in which the Repository Objects sync job is run for the system in SAP GRC. Additionally, it depends on the effective record updated in GRC after all repository object sync jobs are executed. If the option for Enable/Disable users on all the SAP GRC connected-systems is enabled:
- The identity status will be disabled when the user account is disabled on all the systems.
- The identity status will be enabled even if the user account is enabled on any single system.
- If the option for Enable/Disable users on all the SAP GRC connected-systems is disabled:
- The identity status will be disabled only when the user account is disabled on the master system.
- The identity status will be enabled only when the user account is enabled on the master system.
- The Requester ID and Requester Email are automatically set as the Application Owner ID and Email in GRC while placing the Access Request.
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.